| Author |
Message
|
| sbabbar98 |
 Posted: Sun Mar 13, 2005 3:12 pm Post subject: WAS having issues Accessing Cluster Queues |
 |
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
Hello,
I am trying to setup MQ cluster and I am getting the following error :
InvalidDestinationException: MQJMS2008: failed to open MQ queue .
Looks like WebSphere Application Server (WAS) is having issues opening the Cluster queues.It is working Ok on the System where the cluster queues are created local but giving the above error on system where queues are alias.
Any ideas?
Thanks in advance.
SB |
|
| Back to top |
|
 |
| JT |
| Posted: Sun Mar 13, 2005 3:27 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Check your queue destination configuration to ensure the 'Base Queue Manager Name' parameter is empty. If a queue manager is specified, MQ will only look for the queue on that queue manager, and obviously if it's a cluster queue it physically resides elsewhere. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Mar 13, 2005 4:36 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can not use remote queues for MDBs - because you can't GET from a non-local queue.
Clustering doesn't change this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Mar 14, 2005 7:01 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
sbabbar98,
Is this a MDB? Are you doing a PUT or a GET? I only ask because I didn't see in your query where you stated either. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Mar 14, 2005 7:17 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I'd also like to see the linked exception. It will help point to what is wrong. You can search on this site for linked exception to get how to do it. |
|
| Back to top |
|
|
| sbabbar98 |
| Posted: Fri Mar 18, 2005 11:20 pm Post subject: |
|
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
| JT wrote: |
| Check your queue destination configuration to ensure the 'Base Queue Manager Name' parameter is empty. If a queue manager is specified, MQ will only look for the queue on that queue manager, and obviously if it's a cluster queue it physically resides elsewhere. |
'
Thanks much .. This was it .. I removed the " Base Queue Manage Name " and it started working .. Thanks again JT |
|
| Back to top |
|
|
|
|
