Hi I have seen this recently. I think it may have to do with the set up of the queues from the MQ side rather than the jndi set up of the queues on Websphere. In my case our infrastructure people didn't set my MDB's reply queue as a remote queue. So the home/remote queues were deleted and redefined. However I'm not familar with the MQ commands to give you them but I'm sure they can be found on the web.
The Queues are defined in the queue manager, and from the Administrative console I am doing the following :
Click on Servers > Application Servers > servername > Server Components > JMS Server. Then inside the Queue Names text area I enter the names of the queue that are defined in the Queue manager. All the Q names are entered in different lines, no comma or semicolon is used as seperator. Am I doing something wrong here? or am I suppose to do some other settings for the Q? I am using WSAD 5.1.0 and WebSphere MQ 6.0
Thanks, Janhavi
"Weekends don't count unless you spend them doing something completely pointless."
Yes, there is alot. That is not where you want to be at all. Instead, go to resources, Websphere MQ JMS providers and add your QueueConnectionFactory and your QueueDestination (which is a pointer to the actual WMQ queue) then add a MessageListenerPort and attach the QCF and Qdest. Yuo should be set afterwards.
Janhavi, It is also important to make sure that when ever you get JMS Exceptions, you obtain the linked Exception as well like exception.getLinkedException() This will give the specific error code, with which you will come to know the exact mq exception cause by looking up the mqrc details.
