| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS pubsub not working in WAS cluster |
« View previous topic :: View next topic » |
| Author |
Message
|
| dertel |
 Posted: Mon Apr 14, 2008 12:13 pm Post subject: JMS pubsub not working in WAS cluster |
 |
|
Novice
Joined: 17 Dec 2003
Posts: 15
|
We are new to JMS pubsub. After reading many manuals, here is the setup we arrived at: 2 WAS servers in cluster, each with its own queue manager; we created a topic scoped at the WAS cluster level; we created durable subscriptions with the local queue name (SYSTEM.JMS.D.AESAA) on both servers; the name of the durable subscription is configured in WAS topic connection factory.
We used a java program to publish a message to the topic, but we received it only on the local server, and the queue for durable subscription also received the message only on the local server (from where the publish was done). The published message never made it to the remote server in the cluster even though we can see the subscription for the topic on that server (in MQ explorer with supportpac plugin).
We are running MQ 6.0.2.1. WAS servers are z/linux.
Can anyone identify why the message is not subscribed on the remote server? Thank you. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 14, 2008 12:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have to connect the two pub/sub brokers in MQ to each other, one as a child to the other.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dertel |
| Posted: Tue Apr 15, 2008 5:53 am Post subject: |
|
|
Novice
Joined: 17 Dec 2003
Posts: 15
|
We added the parent setting to strmqbrk on one of the qms, and that helped. We then created a durable subscriber on the child using the following code:
TopicSubscriber subscriber = topicSession.createDurableSubscriber(topic, "SYSTEM_D_SUB_AESAA_02");
When we connected to the child and published it worked (both parent and child received the message). When we publish from the parent, the child does not get the message, and the WAS listener on the child fails with the following error:
[4/15/08 9:47:25:311 EDT] 00000015 MDBListenerIm W WMSG0019E: Unable to start MDB Listener AesClusterCacheProducer, JMSDestination jms/aesaa/OSCacheTopic : com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_DUPLICATE_IDENTITY Reason code 3078
Can you see anything that we are missing or doing wrong; thanks. |
|
| 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
|
|
|
|
