- Flexera Community
- :
- Spider
- :
- Spider Knowledge Base
- :
- Operations Manager: Spider OM does not start up with message The WorkNavigator initialisation has fa...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Operations Manager: Spider OM does not start up with message The WorkNavigator initialisation has failed
Operations Manager: Spider OM does not start up with message The WorkNavigator initialisation has failed
Summary
This article provides steps to resolve error 500 in which Operations Manager doesn't start up.
Symptoms
Spider Operations Manager doesn't start up an the web site shows an error 500:
In the Operations Managers server.log you can see that the WorkNavigator wasn't able to initialize:
[#|2017-05-05T10:12:07.829+0200|SEVERE|sun-appserver2.1|ch.bw.worknavigator.server|_ThreadID=10;_ThreadName=main;_RequestID=c309aa98-8cac-474f-b322-8bf6746b99ad;|The WorkNavigator initialisation has failed!
javax.jms.JMSException: [C4090]: Invalid port number. Broker is not available or may be paused: [localhost,-1]
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.checkHostPort(ConnectionImpl.java:510)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:134)
at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:130)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.openConnection(ConnectionInitiator.java:412)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:362)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:210)
at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:158)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:836)
at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1528)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:2363)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:1044)
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:430)
at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:60)
at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:59)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:98)
at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:83)
at ch.bw.worknavigator.server.jms.WNJMSConnectionFactory.createQueueConnection(WNJMSConnectionFactory.java:94)
at ch.bw.worknavigator.server.jms.WNJMSSessionFactory.connectQueue(WNJMSSessionFactory.java:194)
at ch.bw.worknavigator.server.jms.WNJMSSessionFactory.initialise(WNJMSSessionFactory.java:145)
at ch.bw.worknavigator.server.core_impl.hibernate.WNInitialiserImpl.initialise(WNInitialiserImpl.java:222)
at ch.bw.worknavigator.server.initialisation.WNInitialiserImpl.initialise(WNInitialiserImpl.java:43)
at ch.bw.worknavigator.server.initialisation.WNInitialiserServlet.contextInitialized(WNInitialiserServlet.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4655)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:5364)
at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
at com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
at com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192)
at com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1762)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1244)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:971)
at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
at com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
at com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192)
at com.sun.enterprise.web.EmbeddedWebContainer$WebEngine.startChildren(EmbeddedWebContainer.java:497)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1244)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:549)
at org.apache.catalina.startup.Embedded.start(Embedded.java:945)
at com.sun.enterprise.web.WebContainer.start(WebContainer.java:873)
at com.sun.enterprise.web.PEWebContainer.startInstance(PEWebContainer.java:793)
at com.sun.enterprise.web.PEWebContainerLifecycle.onStartup(PEWebContainerLifecycle.java:89)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:449)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:134)
at com.sun.enterprise.server.PEMain.run(PEMain.java:409)
at com.sun.enterprise.server.PEMain.main(PEMain.java:336)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.enterprise.server.PELaunch.main(PELaunch.java:415)
|#]
Cause
During the migration to a new server Operations Manager and its corresponding services haven't been properly shut down therefore Glassfish didn't remove the lock file.
Resolution
Follow these steps:
- Delete the lock file of Glassfish
(default: C:\Program Files (x86)\OperationsManager\3rdparty\Glassfish-2.1.1\domains\domain1\imq\instances\imqbroker\lock) - restart Operations Manager
Products
OM4