| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Possible Subscription Glitch??? |
« View previous topic :: View next topic » |
| Author |
Message
|
| MillsPerry |
 Posted: Wed Aug 06, 2003 7:36 am Post subject: Possible Subscription Glitch??? |
 |
|
Acolyte
Joined: 08 Oct 2001
Posts: 59
Location: ZyQuest, inc.
|
While trying to subscribe to a topic this week, I ran into some strange behavior from WMQI that I would like an explanation for. This is purely for my own peace of mind since I would prefer not to believe that Pub/Sub is a flakey process. 
I tried subscribing a new topic to queue 'xyz' using the regsub utility from service pack IA71, but it didn't show up in the control center subscription list. I tried subscribing that queue to other topics, but still no luck.
We can successfully subscribe the new topic to other queues. The problem queue is remote, so I created an identical remote queue with a different name that pointed to the same destination queue. That one worked just fine.
I have considered whether the first queue, the one I can't subscribe with, might be corrupt, but I have found no evidence of corruption. Furthermore, the same behavior exists on bot my test and production brokers, Different queue managers on different servers.
I have also considered whether you can only subscribe a single topic to a queue, but we have many other subscriptions where multiple topics point to the same queue.
Does anybody have an idea why I can't subscribe with this queue? |
|
| Back to top |
|
 |
| granthmuk |
| Posted: Thu Aug 07, 2003 2:37 am Post subject: |
|
|
Apprentice
Joined: 16 May 2001
Posts: 38
Location: Edinburgh, Scotland
|
| It must be that the Broker thinks the Queue does not exist. Do you get a Broker Response message from your Register Subscriber message? If it fails to register a subscriber you should get a reason code in a Broker Response message. |
|
| Back to top |
|
|
| MillsPerry |
| Posted: Thu Aug 07, 2003 7:20 am Post subject: |
|
|
Acolyte
Joined: 08 Oct 2001
Posts: 59
Location: ZyQuest, inc.
|
I think I have it figured out. It was kicking out a 3151 reason code which, according to the documentation, happens when your subscription matches somebody else's.
The problem with that message is that while the queue name was also used by somebody else's subscription, the topic was different. I wouldn't exactly call that a match.
So to make a long story short, I can't seem to use a queue in a subscription if that queue is also used in somebody else's subscription. Sounds like a pretty good argument for restricting who may register subscriptions. |
|
| 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
|
|
|
|
