MWS 10.7 installation error

Getting below error message while installing MWS 10.7, because of below error I am not able to start MWS service and hence MWS is not accessible. appreciate if someone could suggest any work around.

INFO | jvm 1 | 2021/06/30 17:00:34 | Caused by: java.lang.IllegalStateException: Shutdown in progress
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:66)
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.lang.Runtime.addShutdownHook(Runtime.java:212)
INFO | jvm 1 | 2021/06/30 17:00:34 | at org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:177)
INFO | jvm 1 | 2021/06/30 17:00:34 | at com.softwareag.wsstack.osgi.axis2.internal.plugins.AxisManager.startAxis(AxisManager.java:233)
INFO | jvm 1 | 2021/06/30 17:00:34 | at com.softwareag.wsstack.osgi.axis2.internal.plugins.AxisManager.startImpl(AxisManager.java:147)
INFO | jvm 1 | 2021/06/30 17:00:34 | at com.softwareag.wsstack.osgi.axis2.internal.plugins.AxisManager.access$100(AxisManager.java:75)
INFO | jvm 1 | 2021/06/30 17:00:34 | at com.softwareag.wsstack.osgi.axis2.internal.plugins.AxisManager$2.call(AxisManager.java:129)
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.util.concurrent.FutureTask.run(FutureTask.java:266)
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
INFO | jvm 1 | 2021/06/30 17:00:34 | at java.lang.Thread.run(Thread.java:748)
INFO | jvm 1 | 2021/06/30 17:00:34 | INFO: Getting audit config from it’s default location.
INFO | jvm 1 | 2021/06/30 17:00:34 | WARNING: Audit configuration neither exists, nor could be found on the classpath. Auditing will not work.
INFO | jvm 1 | 2021/06/30 17:00:34 | INFO: Using dummy audit implementation.
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 | Shutdown Manager running all shutdown hooks
INFO | jvm 1 | 2021/06/30 17:00:34 |
INFO | jvm 1 | 2021/06/30 17:00:34 | [ProxyLogManager] setDelegate: org.apache.logging.log4j.jul.LogManager@ec69bd5 → com.softwareag.platform.jul.proxy.DefaultLogManager@3f99bd52
INFO | jvm 1 | 2021/06/30 17:00:35 | [Wed Jun 30 17:00:35 PDT 2021] [INFO] Bootstrap: Stopped
STATUS | wrapper | 2021/06/30 17:00:36 | ← Wrapper Stopped

Hi Ishwar,

can you check if there are other log files which might have more detailed information about this issue?
There should be some more StackTrace in ahead of the one posted.

With the information provided above it is not clear what is happening exactly.

One Guess:
There is already a MWS running and trying to shutdown which is not completing for some reason.
If you find the related process and force it to terminate, then it should be possible to give it anothter try to start MWS.

Regards,
Holger

I have attached the latest log for you to check.

Thanks,

-Ishwar Wagh

image001.jpg

wrapperlog.txt (11.1 KB)

full log.txt (79.8 KB)

platformlog.txt (6.22 KB)

Here is the latest logs from wrapper log file.

jvm 1 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-07-01 14:36:14.373

jvm 1 | !MESSAGE Initialized graceful shutdown handler.

jvm 1 | [ProxyLogManager] setDelegate: com.softwareag.platform.jul.proxy.DefaultLogManager@3f99bd52 → org.apache.logging.log4j.jul.LogManager@45e1163c

jvm 1 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory

jvm 1 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory

jvm 1 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory

jvm 1 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory

jvm 1 | 2021-07-01 14:36:15.636:INFO::Start Level: Equinox Container: 2bdf58b2-644a-487b-87e5-d72dedd19290: Logging initialized @1899ms to org.eclipse.jetty.util.log.StdErrLog

jvm 1 | 2021-07-01 14:36:15.638:WARN:oejob.JettyBootstrapActivator:Start Level: Equinox Container: 2bdf58b2-644a-487b-87e5-d72dedd19290: OSGi support for java.util.ServiceLoader may not be present. You may experience runtime errors.

jvm 1 | 2021-07-01 14:36:15.960:WARN:oejobis.DefaultJettyAtJettyHomeHelper:Start Level: Equinox Container: 2bdf58b2-644a-487b-87e5-d72dedd19290: No default jetty created.

jvm 1 | Shutdown Manager running all shutdown hooks

jvm 1 | [ProxyLogManager] reset() → org.apache.logging.log4j.jul.LogManager@45e1163c

jvm 1 | [STARTUP] Glue 8.0 Fix 9000 build 196

jvm 1 | [Thu Jul 01 14:36:17 PDT 2021] [INFO] Bootstrap: Stopping…

jvm 1 |

jvm 1 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-07-01 14:36:17.773

jvm 1 | !MESSAGE Stopping OSGi framework.

jvm 1 |

jvm 1 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-07-01 14:36:17.786

jvm 1 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.

wrapper | Shutdown failed: Timed out waiting for signal from JVM.

wrapper | JVM did not exit on request, termination requested.

wrapper | JVM received a signal SIGKILL (9).

wrapper | JVM process is gone.

wrapper | JVM exited after being requested to terminate.

wrapper | ← Wrapper Stopped

image001.jpg

Hi Ishwar,

is this a fresh install or was the instance running correctly previously?

Are you using Embedded or External database for the MWS?
When it is external: were the database schema created with Database Configurator prior to first start of MWS?

Regarding the Logs it looks like MWS did not initialize itself correctly during installation and first start:
“No default jetty created”
Jetty is the underlying engine on which MWS is based.

Regards,
Holger

thanks my issue has been fixed.

Hello, can you reply here , what was the action you have taken for this issue.