My Webmethods server is not up

Mahesh_Chiluka1 · July 30, 2016, 3:44pm

Hi guys,

I got the below issue in MWS,when start the MWS I am getting the below messages.

INFO | jvm 1 | 2016/07/30 18:58:21 | !ENTRY com.softwareag.platform.hook.shutdown 32 0 2016-07-30 18:58:21.000
INFO | jvm 1 | 2016/07/30 18:58:21 | !MESSAGE Initialized graceful shutdown handler.
INFO | jvm 1 | 2016/07/30 18:58:21 | Jul 30, 2016 6:58:21 PM com.softwareag.platform.console.internal.LocalConsoleManager open
INFO | jvm 1 | 2016/07/30 18:58:21 | INFO: Local JLine console flag: com.softwareag.platform.console.local.enabled=auto
INFO | jvm 1 | 2016/07/30 18:58:21 | Jul 30, 2016 6:58:21 PM com.softwareag.platform.console.internal.LocalConsoleManager open
INFO | jvm 1 | 2016/07/30 18:58:21 | INFO: Local JLine console disabled: JVM not attached to a terminal.
INFO | jvm 1 | 2016/07/30 18:58:22 | Jul 30, 2016 6:58:22 PM com.softwareag.platform.logging.init.internal.Activator start
INFO | jvm 1 | 2016/07/30 18:58:22 | INFO: Setting configuration directory to /root/softwareAG/softwareAG99/profiles/MWS_default/configuration
INFO | jvm 1 | 2016/07/30 18:58:22 | Jul 30, 2016 6:58:22 PM com.webMethods.sc.config.ConfigurationLogger log
INFO | jvm 1 | 2016/07/30 18:58:22 | INFO: Out-of-band file changes will be monitored every ‘60000’ milliseconds
INFO | jvm 1 | 2016/07/30 18:58:22 | Jul 30, 2016 6:58:22 PM com.softwareag.platform.logging.init.internal.Activator start
INFO | jvm 1 | 2016/07/30 18:58:22 | INFO: Initializing Journal Logger with the greedy JUL bridge
INFO | jvm 1 | 2016/07/30 19:00:11 | [STARTUP] Glue 8.0 Fix 9000 build 108
INFO | jvm 1 | 2016/07/30 19:00:21 | [Sat Jul 30 19:00:20 IST 2016] Bootstrap: Stopping…
INFO | jvm 1 | 2016/07/30 19:00:21 |
INFO | jvm 1 | 2016/07/30 19:00:21 | !ENTRY com.softwareag.platform.hook.shutdown 32 0 2016-07-30 19:00:20.994
INFO | jvm 1 | 2016/07/30 19:00:21 | !MESSAGE Stopping OSGi framework.
ERROR | wrapper | 2016/07/30 19:01:59 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2016/07/30 19:01:59 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2016/07/30 19:01:59 | JVM received a signal SIGKILL (9).
STATUS | wrapper | 2016/07/30 19:01:59 | JVM process is gone.
STATUS | wrapper | 2016/07/30 19:01:59 | JVM exited after being requested to terminate.
STATUS | wrapper | 2016/07/30 19:02:00 | ← Wrapper Stopped

kindly help me some one.

Thanks and Regards
Mahesh

Holger_von_Thomsen · August 1, 2016, 6:08pm

Hi Mahesh,

please provide more details about this issue:

Is there anything in the full.log of this MWS?
Is it the first time starting?
If so, just try to start once more and keep an eye on the full.log meanwhile.

Which version of MWS is this about?
Are there any Fixes applied to this instance?

Regrads,
Holger

Mahesh_Chiluka1 · August 1, 2016, 6:54pm

Hi Holger,

I started 1st time successfully(startup and shutdown completed successfully). When I try to start second time , I am facing the issue. I will check _full_log file once. I will get back to you.

Thanks

Mahesh_Chiluka1 · August 1, 2016, 7:24pm

Hi Holger,

_full_log

2016-08-01 22:40:41 IST (Framework:INFO) - Obtained cluster bootstrap lock
2016-08-01 22:40:41 IST (com.webMethods.portal.system.impl.BuildVersion:INFO) - MWS BuildVersion: 0.0.0.0.0
2016-08-01 22:40:41 IST (com.webMethods.portal.system.impl.BuildVersion:INFO) - MWS InstalledVersion: 9.10.0.0000-0237
2016-08-01 22:40:41 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.ObjectUtil
2016-08-01 22:40:41 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.ThreadUtil
2016-08-01 22:40:41 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.FileUtil
2016-08-01 22:40:41 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.SystemPaths
2016-08-01 22:40:41 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.Debug
2016-08-01 22:40:42 IST (webm.caf:INFO) - My webMethods Server 9.10.0.0000-0237
2016-08-01 22:40:42 IST (com.webMethods.rtl.util.Debug:INFO) - Started sending JDK log messages to Log4J
2016-08-01 22:40:42 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.io.FileIOManager
2016-08-01 22:40:42 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.xml.XMLUtil
2016-08-01 22:40:43 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.xml.XSLProcessorFactory
2016-08-01 22:40:43 IST (Framework:INFO) - Initializing component: com.webMethods.rtl.util.memory.MemoryMonitor
2016-08-01 22:40:43 IST (Framework:INFO) - Loading phase: [phaseID, phaseName] [miePhaseTwo, miePhaseTwo]
2016-08-01 22:40:43 IST (Framework:INFO) - Initializing components of: miePhaseTwo
2016-08-01 22:40:43 IST (Framework:INFO) - Initializing component: com.webMethods.portal.system.boot.StartupManager
2016-08-01 22:40:45 IST (Framework:INFO) - Current DB component level is 47
2016-08-01 22:40:45 IST (Framework:INFO) - Initializing component: com.webMethods.portal.system.cluster.impl.ClusterProvider
2016-08-01 22:40:45 IST (Framework:INFO) - Initializing components of: cluster
2016-08-01 22:40:45 IST (Framework:INFO) - JMS ClientID: mahesh.localdomain.mws.node.mahesh.localdomain-node43725.8507656899585018880
2016-08-01 22:40:45 IST (Framework:WARN) - The hostname (mahesh.localdomain) for the ‘http’ protocol was not a local address. Changed it to: mahesh.localdomain
2016-08-01 22:40:46 IST (Framework:WARN) - The hostname (mahesh.localdomain) for the ‘https’ protocol was not a local address. Changed it to: mahesh.localdomain
2016-08-01 22:40:51 IST (Framework:INFO) - Initializing components of: null
2016-08-01 22:40:52 IST (Framework:INFO) - Initializing server: mahesh.localdomain-node43725
2016-08-01 22:40:52 IST (Framework:INFO) - The hostname for the SOAP Monitor is not specified, using defaults.
2016-08-01 22:40:52 IST (Framework:INFO) - The hostname for the JCR Remoting is not specified, using defaults.
2016-08-01 22:40:52 IST (Framework:INFO) - No registered exception delegate
2016-08-01 22:40:52 IST (Framework:FATAL) - [POP.005.0041] Unable to start server at port number 8585 on host mahesh.localdomain (for: http) , reason : Cannot assign requested address. Perhaps another MWS process is already running?
com.webMethods.portal.system.init.InitializationException: [POP.005.0041] Unable to start server at port number 8585 on host mahesh.localdomain (for: http) , reason : Cannot assign requested address. Perhaps another MWS process is already running?
at com.webMethods.portal.system.cluster.impl.ClusterProvider.isPortAvailable(ClusterProvider.java:411)
at com.webMethods.portal.system.cluster.impl.ClusterProvider.init(ClusterProvider.java:345)
at com.webMethods.portal.system.init.impl.DefaultPhase.initComponent(DefaultPhase.java:117)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:621)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:149)
at com.webMethods.portal.system.init.impl.DefaultPhase.init(DefaultPhase.java:49)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initComponent(DefaultPhaseProvider.java:266)
at com.webMethods.portal.system.impl.BaseProvider.initComponents(BaseProvider.java:621)
at com.webMethods.portal.system.impl.BaseProvider.init(BaseProvider.java:149)
at com.webMethods.portal.system.init.impl.DefaultPhaseProvider.initializePhases(DefaultPhaseProvider.java:91)
at com.webMethods.portal.system.init.impl.ClusterPhaseProvider.initializePhases(ClusterPhaseProvider.java:121)
at com.webMethods.portal.system.init.impl.PartitionPhaseProvider.initializePhases(PartitionPhaseProvider.java:59)
at com.webMethods.portal.system.PortalSystem.init(PortalSystem.java:946)
at com.webMethods.portal.system.PortalSystem.main(PortalSystem.java:868)
at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:57)
at com.webMethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-08-01 22:40:52 IST (Framework:INFO) - Shutdown Manager running all shutdown hooks.

Holger_von_Thomsen · August 1, 2016, 7:32pm

Hi Mahesh,

can you please check if there is another MWS instance already running?


2016-08-01 22:40:45 IST (Framework:WARN) - The hostname (mahesh.localdomain) for the 'http' protocol was not a local address. Changed it to: mahesh.localdomain 
2016-08-01 22:40:46 IST (Framework:WARN) - The hostname (mahesh.localdomain) for the 'https' protocol was not a local address. Changed it to: mahesh.localdomain 
[...]
2016-08-01 22:40:52 IST (Framework:FATAL) - [POP.005.0041] Unable to start server at port number 8585 on host mahesh.localdomain (for: http) , reason : Cannot assign requested address. Perhaps another MWS process is already running? 
com.webmethods.portal.system.init.InitializationException: [POP.005.0041] Unable to start server at port number 8585 on host mahesh.localdomain (for: http) , reason : Cannot assign requested address. Perhaps another MWS process is already running?

Looks like some sort of initialization/configuration issue.

Can you provide your OS Type please?

As it seems to be a fresh installation can you do the following:

uninstall MWS
drop database schema
recreate database schema
reinstall MWS
try to reconfigure it

Regards,
Holger

Mahesh_Chiluka1 · August 1, 2016, 8:27pm

Hi Holger,

I am using the CentOS 7.

Mahesh_Chiluka1 · August 2, 2016, 3:28pm

Hi Holger,

I did

As it seems to be a fresh installation can you do the following:

uninstall MWS
drop database schema
recreate database schema
reinstall MWS
try to reconfigure it

Even I change the port number ‘8585’ to ‘8686’ but still i am facing the same issue.

INFO | jvm 1 | 2016/08/02 18:50:20 | [Tue Aug 02 18:50:20 IST 2016] Bootstrap: Stopped

in wrapper.log

Kindly help me some one. How to resolve this issue.

Holger_von_Thomsen · August 2, 2016, 4:30pm

Hi Mahesh,

sounds really weird now.

I am running out of ideas.

Regards,
Holger