I have installed MQ V7 client in this WAS 6.1.0.21 machine and use the client mode (not binding mode) to connect to the queue.
For some reasons, the servlet can read the first message without the problem; when the thread of reading queue is trying to receive message, I am getting the following exception:
------------------------
[2/26/10 18:06:14:883 PST] 00000032 SystemOut O javax.jms.IllegalStateException: Consumer closed
[2/26/10 18:06:14:883 PST] 00000032 SystemOut O javax.jms.IllegalStateException: Consumer closed
[2/26/10 18:06:14:883 PST] 00000032 SystemOut O at com.ibm.ejs.jms.JMSMessageConsumerHandle.checkOpen(JMSMessageConsumerHandle.java:765)
[2/26/10 18:06:14:884 PST] 00000032 SystemOut O at com.ibm.ejs.jms.JMSQueueReceiverHandle.getOpenQueueReceiver(JMSQueueReceiverHandle.java:245)
[2/26/10 18:06:14:884 PST] 00000032 SystemOut O at com.ibm.ejs.jms.JMSQueueReceiverHandle.getOpenMessageConsumer(JMSQueueReceiverHandle.java:231)
[2/26/10 18:06:14:884 PST] 00000032 SystemOut O at com.ibm.ejs.jms.JMSMessageConsumerHandle.receive(JMSMessageConsumerHandle.java:505)
---------------------
The exception was originated from: Message message = myMessageConsumer.receive(myTimeOut);
The same code is working fine if the servelet is communicating with the WAS embedded MQ provider and also on Tomcat communicating with MQ V7. So I think the code should be fine. The problem may be in the configuration.
Anyone has seen such problem?
I am thinking the problem maybe caused by the following possibilities:
1>
Based on the above IBM support doc has the following:
--------
Using the WebSphere MQ Resource Adapter with WebSphere Application Server
The WebSphere MQ Resource Adapter should not be installed within WebSphere Application Server.
-----------
Does it mean that WAS can NOT have embedded MQ JMS Provider if the code needs to communicate with external MQ JMS Provider?
2> My queue connection factory and queue is defined under
"WebSphere MQ messaging provider" not "V5 default messaging provider". Is it possible the code is using the MQ resource adapter?
Posted: Wed Mar 03, 2010 9:09 pm Post subject: Re: WAS V6.1 and MQ V7 integration
Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
jerrydBrowser wrote:
I am thinking the problem maybe caused by the following possibilities:
1>
Based on the above IBM support doc has the following:
--------
Using the WebSphere MQ Resource Adapter with WebSphere Application Server
The WebSphere MQ Resource Adapter should not be installed within WebSphere Application Server.
-----------
Does it mean that WAS can NOT have embedded MQ JMS Provider if the code needs to communicate with external MQ JMS Provider?
No the message is quite clear: You should not use the MQ RAR with WAS.
You can however use the WAS management console to setup JMS with the WebSphere MQ provider.
jerrydBrowser wrote:
2> My queue connection factory and queue is defined under
"WebSphere MQ messaging provider" not "V5 default messaging provider". Is it possible the code is using the MQ resource adapter?
Thanks in advance!!
Again from the previous entry you should not have installed MQ RAR with WAS. If you did please remove it.
Hope this helps _________________ MQ & Broker admin
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