MWS frequently going down

Hi experts,

Can someone please assist on this case, One of our MWS server down , when i start the MWS, no response.
Can see only the wrapper_log attached down, please verify.

From this SAG directory / MWS/server/default/logs. from this path i cant see any logs like problem_log, full_log.

Wrapper_log:

ENTRY com.softwareag.platform.hook.locations 1 0 2022-12-26 01:09:20.723
INFO | jvm 1 | 2022/12/26 01:09:20 | !MESSAGE Registered location sag.install.area=file:/ngs/app/b2bhrp/apps/wm105_mws/
INFO | jvm 1 | 2022/12/26 01:09:20 | [Mon Dec 26 01:09:20 PST 2022] Bootstrap: Initialized shutdown handler to com.softwareag.platform.hook.shutdown.HookConfiguratorImpl$$Lambda$1/1065410564@4a7aeb18
INFO | jvm 1 | 2022/12/26 01:09:20 |
INFO | jvm 1 | 2022/12/26 01:09:20 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2022-12-26 01:09:20.814
INFO | jvm 1 | 2022/12/26 01:09:20 | !MESSAGE Initialized graceful shutdown handler.
INFO | jvm 1 | 2022/12/26 01:09:22 | [ProxyLogManager] setDelegate: com.softwareag.platform.jul.proxy.DefaultLogManager@33c7353a → org.apache.logging.log4j.jul.LogManager@6ebbc501
INFO | jvm 1 | 2022/12/26 01:09:25 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties. Using default: org.owasp.esapi.reference.JavaLogFactory
INFO | jvm 1 | 2022/12/26 01:09:25 | SecurityConfiguration for ESAPI.Logger not found in ESAPI.properties.
INFO | jvm 1 | 2022/12/26 01:09:34 | [ProxyLogManager] reset() → org.apache.logging.log4j.jul.LogManager@6ebbc501
INFO | jvm 1 | 2022/12/26 01:09:35 | [Mon Dec 26 01:09:35 PST 2022] Bootstrap: Stopping…
INFO | jvm 1 | 2022/12/26 01:09:35 |
INFO | jvm 1 | 2022/12/26 01:09:35 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2022-12-26 01:09:35.247
INFO | jvm 1 | 2022/12/26 01:09:35 | !MESSAGE Stopping OSGi framework.
INFO | jvm 1 | 2022/12/26 01:09:35 |
INFO | jvm 1 | 2022/12/26 01:09:35 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2022-12-26 01:09:35.250
INFO | jvm 1 | 2022/12/26 01:09:35 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.
ERROR | wrapper | 2022/12/26 01:11:10 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2022/12/26 01:11:10 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2022/12/26 01:11:10 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2022/12/26 01:11:10 | JVM process is gone.
STATUS | wrapper | 2022/12/26 01:11:10 | JVM exited after being requested to terminate.
STATUS | wrapper | 2022/12/26 01:11:11 | ← Wrapper Stopped

Please assist to bring up the MWS

1 Like

MWS.DB.Xml file, user password is expired. Renewed the password and updated in mws.db.xml file and started.
Now MWS is running fine.

1 Like

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.