Dear Team,
Currently we are facing an issue in bringing the MWS Server up. The webMethods version we are using in 10.5. Steps followed to bring MWS Server up is

1. Navigated to location: SoftwareAG\MWS\bin . And executed the script startup.bat. The server did not come up.
2. Navigated to location: SoftwareAG\profiles\MWS_mwsinstance01\bin . And executed the script startup.bat. The server did not come up.
3. We also tried to executed the script with -safeboot option. Despite applying the option, the server did not come yp.
4. We have also made sure that the database are connected to webMethods (Oracle external database).
5. The table are also created using the dbconfigurator.bat
   Please find the attached logs and configuration file. Hope to get the response of the error at the earliest.

INFO | jvm 1 | 2021/03/24 09:17:31 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-03-24 09:17:31.717
INFO | jvm 1 | 2021/03/24 09:17:31 | !MESSAGE Stopping OSGi framework.
INFO | jvm 1 | 2021/03/24 09:17:31 |
INFO | jvm 1 | 2021/03/24 09:17:31 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-03-24 09:17:31.719
INFO | jvm 1 | 2021/03/24 09:17:31 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.

Hi Subhajit,

please check your SoftwareAG\MWS\server\default\logs dir if there is a full.log and examine this one.

Upon first start the MWS takes much longer than usual as it needs to initialize all of the predeployed portles and the user database.

From the provided log snippet I cannot recognize any error.

Regards,
Holger

Thank you for the response, but it’s still getting shutdown. Please find the attached logs.

INFO | jvm 1 | 2021/03/24 09:17:31 | [Wed Mar 24 09:17:31 IST 2021] Bootstrap: Stopping…
INFO | jvm 1 | 2021/03/24 09:17:31 |
INFO | jvm 1 | 2021/03/24 09:17:31 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-03-24 09:17:31.717
INFO | jvm 1 | 2021/03/24 09:17:31 | !MESSAGE Stopping OSGi framework.
INFO | jvm 1 | 2021/03/24 09:17:31 |
INFO | jvm 1 | 2021/03/24 09:17:31 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2021-03-24 09:17:31.719
INFO | jvm 1 | 2021/03/24 09:17:31 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.
ERROR | wrapper | 2021/03/24 09:19:14 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2021/03/24 09:19:14 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2021/03/24 09:19:14 | JVM exited after being requested to terminate.
STATUS | wrapper | 2021/03/24 09:19:15 | ← Wrapper Stopped

MWS is automatically getting shutdown after 120 seconds, no matter what we try, it is getting shutdown.

Hi,

once more:
the provided log snippet is not help full at the moment.
Please check the other logs in the same directory as the wrapper log and/or the full.log from the MWS/server/MWS_mwsinstance01/logs directory.

Looks like the shutdown gets triggered by some deeper issue documented somewhere else.

Regards,
Holger

I am not able to find full.log and since I am new to this forum, the tool is not allowing me upload any document. That being said, I am pasting the logs which I have retrieved from sag-osgi.log .

2021-03-24 22:27:53,542 INFO [Configuration ] - 010
2021-03-24 22:27:53,779 WARN [OPM.Master Password ] - mpw.except
2021-03-24 22:27:53,780 WARN [OPM.Master Password ] - mpw.except
2021-03-24 22:27:55,042 WARN [OPM ] - passman.badLCD
2021-03-24 22:27:55,155 WARN [OPM ] - passman.badExpireInt
2021-03-24 22:27:55,442 INFO [com.s.p.j.i.Activator ] - LoginModuleFactoryRegistry opened
2021-03-24 22:27:55,448 INFO [com.s.p.j.i.Activator ] - ManagedServiceFactory serice registered com.softwareag.platform.jaas.internal.ManagedConfiguration@6c27bc9e
2021-03-24 22:27:55,535 INFO [com.s.p.j.e.i.LoginModuleBundleTracker ] - Processing bundle com.softwareag.security.authz.store(10.5.0.0000-0229)
2021-03-24 22:27:55,557 INFO [com.s.s.s.i.e.ESAPIConfigurator ] - Using ‘file:/C:/SoftwareAG/profiles/MWS_default/configuration//ESAPI.properties’
2021-03-24 22:27:55,558 INFO [com.s.s.s.i.e.ESAPIConfigurator ] - Using internal ESAPI.properties
2021-03-24 22:27:55,581 INFO [com.s.p.j.e.i.LoginModuleBundleTracker ] - Processing bundle com.softwareag.security.sin.idp.saml.lm(10.5.0.0000-0229)
2021-03-24 22:27:55,586 INFO [com.s.p.j.e.i.LoginModuleBundleTracker ] - Processing bundle com.softwareag.security.sin.is.ldap(10.5.0.0000-0229)
2021-03-24 22:27:55,606 INFO [com.s.p.j.e.i.LoginModuleBundleTracker ] - Processing bundle com.softwareag.security.sin.misc(10.5.0.0000-0229)
2021-03-24 22:27:55,631 INFO [com.s.p.j.e.i.LoginModuleBundleTracker ] - Processing bundle com.softwareag.security.web.sso.saml2(10.5.0.0000-0229)
2021-03-24 22:27:55,701 INFO [org.e.j.u.log ] - Logging initialized @10147ms
2021-03-24 22:27:57,804 WARN [org.e.j.o.b.i.s.DefaultJettyAtJettyHomeHelper ] - No default jetty created.
2021-03-24 22:27:57,923 INFO [com.s.w.o.a.s.i.TransportListenerRegistryManager ] - WSSOGI0030: updated( null )
2021-03-24 22:28:00,725 INFO [com.w.p.PortalException ] - No registered exception delegate
2021-03-24 22:28:00,814 ERROR [com.w.p.s.i.PortalSystemActivator ] - [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

com.webMethods.portal.system.init.InitializationException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at com.webmethods.portal.service.sql.core.ConnectionManager.validateDatasource(ConnectionManager.java:742) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:355) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:277) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.initDbConnection(ClusterPhaseProvider.java:321) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.initializeDatabaseConfigLocator(ClusterPhaseProvider.java:309) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.preInit(ClusterPhaseProvider.java:73) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.system.impl.PortalSystemActivator.start(PortalSystemActivator.java:76) [com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:815) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:808) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_222]
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:808) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:765) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.Module.doStart(Module.java:589) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.Module.start(Module.java:457) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1784) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1764) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1726) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1657) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) [org.eclipse.osgi_3.13.300.0000-0004.jar:3.13.300.0000-0004]

Caused by: java.sql.SQLSyntaxErrorException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

at com.wm.dd.jdbc.oraclebase.ddcj.a(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oraclebase.ddcj.a(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oraclebase.ddcj.a(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oracle.ddal.a(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oracle.ddal.a(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oracle.ddam.u(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oraclebase.dder.y(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oraclebase.dder.x(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.wm.dd.jdbc.oraclebase.dder.executeQuery(Unknown Source) ~[com.softwareag.ext.dd.cjdbc_6.0.0.0001-0002.jar:?]
at com.webmethods.portal.service.sql.core.BaseSqlWorker.executeQuery(BaseSqlWorker.java:607) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
at com.webmethods.portal.service.sql.core.ConnectionManager.validateDatasource(ConnectionManager.java:733) ~[com.webmethods.caf.server_10.5.0.0000-0232.jar:10.5.0.0000-0232]
... 22 more

2021-03-24 22:28:01,848 INFO [org.e.e.logger ][0] - Stopping OSGi framework.
2021-03-24 22:28:01,851 INFO [org.e.e.logger ][0] - Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.

Hi Subhajit,

looks like MWS is not able to connect to the database as the schema being referenced in mws.db.xml does not contain the required tables.

Are you sure that the tables etc. where successfully created using DB Configurator before trying to start the MWS for the first time?

Regards,
Holger

Yes, before trying to start the MWS for the first time, I have successfully created using DB configurator. And I am using oracle & I have also used jdbc:wm:oracle://localhost:1521;serviceName=XE this url for configurating Database. Still MWS is not starting properly.

I have seen this error before. Holger is right, it looks like an missing or wrong DB schema. Recommendation is to drop and re-create it, especially the objects for MWS.

Hi Subhajit,

Please check if the latest DCC fixes are available and required MWS fixes are in place. If you are sure you did the first time right, then having a check with fixes might help. Drop all tables and create a new schema to run the latest MWS component on DCC.

Hope once this is done you should be able to initiate the MWS once, before starting it directly.

Regards,
Firoz N

Hi Firoz,
could you please brief about DCC fixes and where it is available.
I also got the same problem “My MWS is not bringing up” it shows timeout error

INFO | jvm 1 | 2023/07/23 00:20:48 | 2023-07-23 00:20:48,819 Start Level: Equinox Container: 73c284a8-2690-4c4b-bdfb-abade87e92be ERROR Unrecognized conversion specifier [scgMsgKey] starting at position 37 in conversion pattern.
INFO | jvm 1 | 2023/07/23 00:20:49 | [ProxyLogManager] reset() → org.apache.logging.log4j.jul.LogManager@189ebfeb
INFO | jvm 1 | 2023/07/23 00:20:50 | [Sun Jul 23 00:20:50 PDT 2023] Bootstrap: Stopping…
INFO | jvm 1 | 2023/07/23 00:20:50 |
INFO | jvm 1 | 2023/07/23 00:20:50 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2023-07-23 00:20:50.351
INFO | jvm 1 | 2023/07/23 00:20:50 | !MESSAGE Stopping OSGi framework.
INFO | jvm 1 | 2023/07/23 00:20:50 |
INFO | jvm 1 | 2023/07/23 00:20:50 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2023-07-23 00:20:50.355
INFO | jvm 1 | 2023/07/23 00:20:50 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.
INFO | jvm 1 | 2023/07/23 00:20:50 | [STARTUP] Glue 8.0 Fix 9000 build 161
ERROR | wrapper | 2023/07/23 00:22:24 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2023/07/23 00:22:24 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2023/07/23 00:22:24 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2023/07/23 00:22:24 | JVM process is gone.
STATUS | wrapper | 2023/07/23 00:22:24 | JVM exited after being requested to terminate.
STATUS | wrapper | 2023/07/23 00:22:24 | ← Wrapper Stopped

Hi,

please focus on this error message:

Please check for the fixes as requested above.

Regards,
Holger