Hello,

I am facing issue while rebooting the server, the below is shown in the logs and it gets stuck there.
After line “Initializing components of: mechanics” it does not show anything else.

2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.service.meta2.impl.MetaManager
2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing components of: meta
2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing components of: default
2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.ThingIDService
2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.ThingService
2016-08-25 15:45:16 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.XTypeService
2016-08-25 15:45:17 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.dbo.DBOStorageService
2016-08-25 15:45:17 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.MetaQueryService
2016-08-25 15:45:17 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.TypeService
2016-08-25 15:45:17 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.UserService
2016-08-25 15:45:17 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.RelationService
2016-08-25 15:45:18 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.MetaEventService
2016-08-25 15:45:18 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.MetaViewService
2016-08-25 15:45:18 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.AccessService
2016-08-25 15:45:18 IST [CommonLib.MWS.0002I] Initializing com.webMethods.portal.service.meta2.impl.ServiceThingService
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.mech.alias.impl.AliasMechanics
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Loading phase: [phaseID, phaseName] [CoreServices, CoreServices]
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing components of: CoreServices
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.service.dir.impl.DirSystem
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing components of: directory
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.service.portlet.impl.PortletProvider
2016-08-25 15:45:19 IST [CommonLib.MWS.0002I] Initializing components of: portlet
2016-08-25 15:45:44 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.event.EventDeliveryInitializer
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Created New subscription: 387 for TCS467432.TCSERICSSON.COM.mws.library.5216574714314631168.com.webMethods.nis.events
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.bizPolicy.impl.ContextProvider
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Initializing components of: context
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Loading phase: [phaseID, phaseName] [mechanics, mechanics]
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Initializing components of: mechanics
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Initializing component: com.webMethods.portal.mech.impl.MechanicsManager
2016-08-25 15:45:45 IST [CommonLib.MWS.0002I] Initializing components of: mechanics

I tried comparing the /bin/ini,cnf file with other server, no difference i found.
I also tried restoring the entire config from back up folder, but no luck.

Please help.

Regards,
Nikhil Pardeshi

Hi Nikhil,

was MWS started at lease once before starting IS?

Was this already working in the past?

Where there any Fixes applied recently?

Please provide your wM version.

Please check the Wrapper logs under profiles/IS/logs for further error messages.

Regards,
Holger

Hello Holger,

The IS came up later, but it taikes some time around 15 mins after that line which i mentioned above.
My WM version is 9.9

Hi Nikhil,

this is a long period.

I am not sure if this is due to wM 9.9 or some other issues.

Even when there are lof of packages and nodes deployed to the IS it should not take tht long.

For my wM 9.5 environments the startup time is between less than 2 minutes (empty server) and not more than 8 minutes (our largest instance).

Regards,
Holger

Hi Nikhil,

You can check from server log, if any of your custom package loading is taking much time which may contain start up serrvices.

Hello,

Package loading is not taking much time. As I mentioned above it gets stuck at the above line.
It was working normally before but after linking IS with MWS, it started taking long time.

Regards,
Nikhil Pardeshi

Hi Nikhil,

increase the log level to trace for the integrationserver and start again.

Most likely there is an issue with connection from IS to MWS resulting in retries.

Please check the MWS full.log for further informations.

Regards,
Holger

Can you also share the wrapper.log under profiles of Integration Server?

Hello Holger/Srikanth,

Attaching the wrapper logs captured at the time when it gets stuck while booting up.
wrapper log.txt (8.55 KB)

Hi,

INFO | jvm 2 | 2016/09/01 18:33:38 |
INFO | jvm 2 | 2016/09/01 18:33:38 | !ENTRY org.eclipse.equinox.cm 4 0 2016-09-01 18:33:38.401
INFO | jvm 2 | 2016/09/01 18:33:38 | !MESSAGE directory : Failed to get canonical path from: @path:osgi.configuration.area/event/routing/bundles
INFO | jvm 2 | 2016/09/01 18:33:38 | !STACK 0
INFO | jvm 2 | 2016/09/01 18:33:38 | java.io.IOException: The filename, directory name, or volume label syntax is incorrect
INFO | jvm 2 | 2016/09/01 18:33:38 | at java.io.WinNTFileSystem.canonicalize0(Native Method)
INFO | jvm 2 | 2016/09/01 18:33:38 | at java.io.WinNTFileSystem.canonicalize(WinNTFileSystem.java:428)
INFO | jvm 2 | 2016/09/01 18:33:38 | at java.io.File.getCanonicalPath(File.java:618)
INFO | jvm 2 | 2016/09/01 18:33:38 | at java.io.File.getCanonicalFile(File.java:643)
INFO | jvm 2 | 2016/09/01 18:33:38 | at com.softwareag.platform.bundle.watchdog.internal.Utils.readFile(Utils.java:71)
INFO | jvm 2 | 2016/09/01 18:33:38 | at com.softwareag.platform.bundle.watchdog.internal.BundleWatchdogsLifecycle$BundleWatchdogScope.(BundleWatchdogsLifecycle.java:166)
INFO | jvm 2 | 2016/09/01 18:33:38 | at com.softwareag.platform.bundle.watchdog.internal.BundleWatchdogsLifecycle.updated(BundleWatchdogsLifecycle.java:92)
INFO | jvm 2 | 2016/09/01 18:33:38 | at org.eclipse.equinox.internal.cm.ManagedServiceFactoryTracker$2.run(ManagedServiceFactoryTracker.java:190)
INFO | jvm 2 | 2016/09/01 18:33:38 | at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)

I can see the above error from the error logs

Can you try to delete the profile and re-create it using the instance commands?

from the wrapper logs, it looks like some issue while loading the files, may be due to corruption of jar files. Can you work in this corner and update us.

Thanks,