Software AG My Webmethods Server service not starting

Hi,

The My Webmethods Server service will not start. The Integration Server service is up, and I’ve tested the JDBC connections successfully.

None of the application logs, or the event viewer, appear to provide any useful information as to why the My Webmethods Server service will not start.

Any ideas on what the issue might be, or where I should be looking in order to troubleshoot this issue?

Thanks,

Ken

Hi Ken,

please check for the profile/MWS_default/logs/wrapper.log for messages.
Additionally you should check the MWS/server/default/logs/full.log for errors.

Did you check the mws.db.xml for correct entries?
Was the MWS started at least once successfully?

What is your exact version incl. Fixes applied to this installation?

Regards,
Holger

Hi Holger,

Thank you for the suggestions. The mws.db.xml file appears to have the correct entries, and the connection tested successfully. MWS was started at least once successfully. Our exact version is 10.1. We have the following fixes installed: MWS_10.1.0_Fix8 and Trading Networks UI 10.1 Fix 4.

Both the profile/MWS_default/logs/wrapper.log and MWS/server/default/logs/full.log files were difficult to understand; however the following stood out.

From the wrapper.log file:
INFO | jvm 1 | 2019/10/29 13:31:06 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2019-10-29 13:31:06.664
INFO | jvm 1 | 2019/10/29 13:31:06 | !MESSAGE Initialized graceful shutdown handler.
INFO | jvm 1 | 2019/10/29 13:41:32 | move: failed to rename E:\SoftwareAG101\profiles\MWS_default\configuration\org.eclipse.osgi\bundleFile6722896247631019393.tmp to E:\SoftwareAG101\profiles\MWS_default\configuration\org.eclipse.osgi\608\0\bundleFile
INFO | jvm 1 | 2019/10/29 13:41:32 | [Tue Oct 29 13:41:32 MDT 2019] Bootstrap: Stopping…
INFO | jvm 1 | 2019/10/29 13:41:32 |
INFO | jvm 1 | 2019/10/29 13:41:32 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2019-10-29 13:41:32.954
INFO | jvm 1 | 2019/10/29 13:41:32 | !MESSAGE Stopping OSGi framework.
INFO | jvm 1 | 2019/10/29 13:41:32 |
INFO | jvm 1 | 2019/10/29 13:41:32 | !ENTRY com.softwareag.platform.hook.shutdown 1 0 2019-10-29 13:41:32.956
INFO | jvm 1 | 2019/10/29 13:41:32 | !MESSAGE Framework shutdown timeout set to 120 seconds. Please also check tanuki-wrapper shutdown property, if specified.
INFO | jvm 1 | 2019/10/29 13:41:33 | [Tue Oct 29 13:41:33 MDT 2019] Bootstrap: Stopped
STATUS | wrapper | 2019/10/29 13:41:35 | <-- Wrapper Stopped

From the full.log file:
2019-10-29 13:41:31 MDT (c.w.p.PortalException:INFO) [MWS Startup-1] - No registered exception delegate
2019-10-29 13:41:31 MDT (c.w.p.s.PortalSystem:TRACE) [MWS Startup-1] - getComponentProvider: no name supplied for com.webmethods.portal.service.global.IGlobalProvider so using null as the name
2019-10-29 13:41:31 MDT (c.w.p.s.i.i.PartitionPhaseProvider:ERROR) [MWS Startup-1] - Required OSGi service was not found: {interface=com.webmethods.portal.service.meta2.IMetaManager, timeout=600}
javax.jms.IllegalStateException: Required OSGi service was not found: {interface=com.webmethods.portal.service.meta2.IMetaManager, timeout=600}
2019-10-29 13:41:31 MDT (c.w.r.p.ShutdownManager:INFO) [Thread-14] - Shutdown Manager running all shutdown hooks.

Will be doing some digging in empower to try to understand what the log messages mean.

Thanks,

Ken

This issue is now resolved. Our IT team worked with Software AG. The solution required taking a backup of MWS and re-creating the OSGI profile.