aspose file tools*
The moose likes Websphere and the fly likes JMS Issue with WAS 5.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "JMS Issue with WAS 5.1" Watch "JMS Issue with WAS 5.1" New topic
Author

JMS Issue with WAS 5.1

Jaideep Joshi
Greenhorn

Joined: Mar 12, 2004
Posts: 18
Hi all,
Lot of people seem to have this issue and nobody seems to know the exact reason, so posting this here. Help needed ...
Steps:
1. I created a Queue Connection Factory in 'WebSphere JMS Provider'.
2. I created a Queue in 'WebSphere JMS Provider'.
3. I created a Message Listener Port in server1/Message Listener Service
4. I have one MDB, ibm-ejb-jar-bnd.xml has an entry for this message listener port.
5. When I deploy my application. Server throws following error while starting the application:
[3/24/04 18:37:02:724 EST] 66318893 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/queue/InQueueConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue
[3/24/04 18:37:02:724 EST] 66318893 MDBListenerIm W WMSG0019E: Unable to start MDB Listener MessageProcessorBean, JMSDestination jms/queue/InQueue : javax.jms.JMSException: MQJMS2008: failed to open MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:460)
at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:277)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:112)
at com.ibm.mq.jms.MQQueueConnection.createConnectionBrowser(MQQueueConnection.java:775)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:444)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:362)
at com.ibm.mq.jms.MQQueueConnection.createConnectionConsumer(MQQueueConnection.java:712)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createConnectionConsumer(JMSQueueConnectionHandle.java:117)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:390)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:553)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:527)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:809)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1527)
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1579)
at com.ibm.mq.jms.MQQueueAgent.resolveQueue(MQQueueAgent.java:451)
at com.ibm.mq.jms.MQQueueAgent.getQueueAgent(MQQueueAgent.java:271)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:277)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:112)
at com.ibm.mq.jms.MQQueueConnection.createConnectionBrowser(MQQueueConnection.java:775)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:444)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:362)
at com.ibm.mq.jms.MQQueueConnection.createConnectionConsumer(MQQueueConnection.java:712)
at com.ibm.ejs.jms.JMSQueueConnectionHandle.createConnectionConsumer(JMSQueueConnectionHandle.java:117)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:390)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:553)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:527)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:809)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Suttan Pym
Ranch Hand

Joined: Jan 30, 2003
Posts: 46
Hi,
When you create a Queue, there is one more thing you have to do. i.e. Go to the location Appserver-> server1-> serverComponents->jmsserver. In this place there is an attribute QueueNames. Any queue you create has to be added in this location also. This is only required for Queues, but not required for Topics.
Suttan
 
Don't get me started about those stupid light bulbs.
 
subject: JMS Issue with WAS 5.1