| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message from Was5.1 to clusterqueue disappears |
« View previous topic :: View next topic » |
| Author |
Message
|
| messie |
 Posted: Wed Oct 19, 2005 2:29 pm Post subject: Message from Was5.1 to clusterqueue disappears |
 |
|
Newbie
Joined: 19 Oct 2005
Posts: 3
|
Hi,
we're implementing an ESB infrastructure with WAS5.1 and MQ5.3. Each WAS node has his own local queue manager instance on the same box. (QM_WASn). JMS accesses QM_WASn in client mode (authentication on application level os required).
There is a seperate box with a MQ instance acting as gateway and cluster repository (QM_HUB).
A local queue LQ.TEST.LOCAL is defined on QM_WASn.
A local queue LQ.TEST.CLUSTER is defined on QM_HUB. This queue has been marked as cluster queue.
The following happens:
To test the MQ config, we put a message to both queue's with the MQ Control Center, both messages arrive at the expected queue and the expected queumanager.
On the WAS server resides an application that put's messages on the queue's (via JMS etc). When a message is put on LQ.TEST.LOCAL it arrives. When a message is put on LQ.TEST.CLUSTER no errors are displayed but the message is nowhere to be found (not in dead letter queue, not in transmit queue, nowhere).
So we connected to QM_WASn with WMQTool and we could not see LQ.TEST.CLUSTER.
Finally we wrote a POJO (plain old java) application that connects to QM_WASn as client and puts a message in both queue's, and lo and behold: both messages arrive.
What's happening? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Oct 19, 2005 5:04 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
So LQ.TEST.CLUSTER is a cluster queue in a cluter that includes QM_HUB (the FR) and QM_WASn (PR's). Its defined as a qlocal in QM_HUB.
If you use MQ Explorer connected to QM_WASn, you can put messages to the queue and they arrive on QM_HUB. You can also do this with a stand-alone java program (JMS or MQ classes?). But using WAS JMS it fails (altohugh you can put to LQ.TEST.LOCAL).
Correct?
_________________
-wayne |
|
| Back to top |
|
|
| messie |
| Posted: Wed Oct 19, 2005 9:46 pm Post subject: |
|
|
Newbie
Joined: 19 Oct 2005
Posts: 3
|
Yes, indeed.
The POJO program use MQ libraries, WAS uses JMS/MQ libraries.
We have been using WAS and MQ for years now and are migrating to a clustered solution for HA/scalability reasons. So we're wondering why software that worked for years does not work when migrated. |
|
| Back to top |
|
|
| messie |
| Posted: Thu Oct 20, 2005 4:11 am Post subject: |
|
|
Newbie
Joined: 19 Oct 2005
Posts: 3
|
it has been solved.
In previous installations wihout a cluster the Queue Definitions within the WAS were always configured with a base queuemanager. Empty this field and voila, it worls. |
|
| 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
|
|
|
|
