| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MSGS0115E: Queue Manager Listener failed rc: 20(help me) |
« View previous topic :: View next topic » |
| Author |
Message
|
| bikkina |
 Posted: Tue Apr 27, 2004 11:44 pm Post subject: MSGS0115E: Queue Manager Listener failed rc: 20(help me) |
 |
|
Newbie
Joined: 28 Mar 2004
Posts: 7
|
Hi,
I am having embedded java messaging service for Websphere application server 5.1.
It is on AIX when i install jms(with WAS )
and start the Websphere application server 5.1(startServer.sh) it is working fine.
suddenly i start today the Websphere application server again((startServer.sh)) i am facing the below error
plz throw some light on this...
Thxs,
Kiran Bikkina.
****************************************************
[4/28/04 12:14:22:166 GMT+05:30] 6eeb7172 JMSService E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0115E: Queue Manager Listener failed rc: 20
at com.ibm.ws.messaging.QueueManagerManager.pingQueueManager(QueueManagerManager.java:702)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.ping(JMSEmbeddedProviderImpl.java:277)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:201)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[4/28/04 12:14:22:205 GMT+05:30] 6eeb7172 ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.messaging.JMSService]
com.ibm.ws.exception.RuntimeWarning: MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0115E: Queue Manager Listener failed rc: 20
at com.ibm.ws.messaging.JMSService.start(JMSService.java:295)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
************************************************************ |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Wed Apr 28, 2004 4:50 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Couple of things.
---From the manuals
20 An error occurred during processing
Which means something went wrong with the listener. To figure out what happened you could look in the error logs, fd files, system error logs or events depending on the platform for the cause.
---Try stopping and restarting it, if it comes up ok and you able to connect to your qm, then you could very well ignore this error and carry on.
Just means that listener had to exit with error code 20(some error internally).
Cheers
Kumar |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Apr 28, 2004 5:17 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| My guess would be that the listener was already running when the qmgr tried to startup. You weren't trying to do anything outside of the WAS environment with your qmgr? I'd suggest that the next time you have your AppServer down, issue a netstat -a. You can check to see if the listener is running. I believe the default port is 5558. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
