| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRCCF_SUBSCRIPTION_LOCKED Reason code 3156 |
« View previous topic :: View next topic » |
| Author |
Message
|
| ArvindC |
 Posted: Wed Feb 26, 2003 3:09 am Post subject: MQRCCF_SUBSCRIPTION_LOCKED Reason code 3156 |
 |
|
Novice
Joined: 25 Dec 2002
Posts: 14
Location: India
|
I am running a test on WebSphereMQ 5.30 on Win2k. I am getting the following exception when I try to start run the 2nd instance of a test program, which basically subscribes to a topic. The program runs fine if I run only one instance of it. Can someone tell what the exception means and how can I resolve it.
Exception:
Got exception com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_LOCKED Reason code 3156
com.ibm.mq.jms.BrokerCommandFailedException: Broker command failed: MQRCCF_SUBSCRIPTION_LOCKED Reason code 3156
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:1399)
at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:571)
at com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:776)
at com.ibm.mq.jms.MQTopicSession.createDurableSubscriber(MQTopicSession.java:615)
Thanks in advance,
Arvind. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Feb 26, 2003 4:41 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I haven't seen this error before, but I would guess that it is caused by the fact that your second subscriber is using the same id as the first. Because it is a durable subscription, the first subscriber has the queue locked and the second one can't get at it. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Wed Feb 26, 2003 4:45 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
I too have not seen that error, but, it looks like your first subscriber has exclusive access.
"The concepts of shared and exclusive access to a subscription are supported by the broker in much the same way as shared and exclusive access to MQSeries objects is supported by a queue manager."
Check the registration options for your first subscriber and/or make sure the second subscriber has the same identity as the first.
I got this info from the book with the latest pub/sub support pac:
http://www-3.ibm.com/software/ts/mqseries/txppacs/ma0c.html
Regards,
Vicky |
|
| Back to top |
|
|
| ArvindC |
| Posted: Thu Feb 27, 2003 2:27 am Post subject: |
|
|
Novice
Joined: 25 Dec 2002
Posts: 14
Location: India
|
The exception occurs when I try to run more than one instance of the client application within the same JVM instance. So, I the problem doesn't seem to be of registration options. Rather it seems to be a problem with the mq java/jms client classes. Has any one tried to run more than one instance of a client application in the same JVM instance? Is it supported in the WebSphere MQ 5.3?
-Arvind |
|
| Back to top |
|
|
| kingdon |
| Posted: Thu Feb 27, 2003 6:42 am Post subject: |
|
|
Acolyte
Joined: 14 Jan 2002
Posts: 63
Location: UK
|
Are you using different clientIDs for the different instances? The JMS spec' requires there to be only one active subscriber for a given durable subscription at any one time. If you want two instances then they need to use different subscriptions, which would normally be done by setting different clientIDs.
You can set the clientID either on the TopicConnectionFactory (so that you can do it administratively) or on a TopicConnection (so you can do it at runtime). Details in the Using Java manual, and restricitons on when you can set the clientID at runtime in the JMS spec.
Regards,
James. |
|
| 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
|
|
|
|
