| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Identifying Orphan Subscriptions with MQ Pub/Sub Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| hilltops |
 Posted: Thu Nov 20, 2008 10:24 am Post subject: Identifying Orphan Subscriptions with MQ Pub/Sub Broker |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
How does one identify which subscriptions have become orphan with a pub/sub broker? I have used the tool amqspsd against my queue manager to view the set of subscriptions, but how does one know which of these are orphans? Below is a sample output from my queue manager/broker domain. Is it possible to tell, looking at the below which have become orphaned?
Topic: FinanceNews\*
BrokerCount: 0
ApplCount: 4
AnonymousCount: 0
RegistrationQMgrName: MYQMGR
RegistrationQName: SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D51204C47424C58303050554220209E2C034907D55023
RegistrationUserIdentifier: mquser
RegistrationOptions: 1025 : MQREGO_CORREL_ID_AS_IDENTITY MQREGO_NON_PERSISTENT
RegistrationTime: 2008112007202915
SubscriptionUserData:
RegistrationQMgrName: MYQMGR
RegistrationQName: SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D51204C47424C58303050554220209E2C034907D45023
RegistrationUserIdentifier: mquser
RegistrationOptions: 1025 : MQREGO_CORREL_ID_AS_IDENTITY MQREGO_NON_PERSISTENT
RegistrationTime: 2008112007202915
SubscriptionUserData:
RegistrationQMgrName: MYQMGR
RegistrationQName: SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D51204C47424C58303050554220204347C54805632225
RegistrationUserIdentifier: mquser
RegistrationOptions: 1025 : MQREGO_CORREL_ID_AS_IDENTITY MQREGO_NON_PERSISTENT
RegistrationTime: 2008102114420827
RegistrationQMgrName: MYQMGR
RegistrationQName: SYSTEM.JMS.ND.SUBSCRIBER.QUEUE
RegistrationCorrellId: 414D51204C47424C58303050554220204347C548075F2225
RegistrationUserIdentifier: mquser
RegistrationOptions: 1025 : MQREGO_CORREL_ID_AS_IDENTITY MQREGO_NON_PERSISTENT
RegistrationTime: 2008102114420825
Thankx |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Nov 21, 2008 7:33 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The way that we've always told was by queue growth. If the subscriber was orphaned, the queue depth kept growing. |
|
| Back to top |
|
|
| battie |
| Posted: Sun Nov 23, 2008 6:40 pm Post subject: Identifying Orphan Subscriptions with MQ Pub/Sub Broker |
|
|
Newbie
Joined: 04 Feb 2007
Posts: 8
Location: Sydney
|
It's difficult if you're using the default SYSTEM.JMS queues as all subscriptions share the same queue. The orphan can be identified by cross checking the RegistrationCorrellId value output from the amqspsd command with the correlation ids of the messages on the SYSTEM.JMS.ND.SUBSCRIBER.QUEUE that you're using. You'll then need to manually deregister the subscriber and remove the unwanted messages.
A better solution is to use a dynamic queue and have one queue per subscriber. This can be either set on the URI or by setting the subscriber queue to SYSTEM.JMS.ND.* using the JMSAdmin tool.
_________________
Battie |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 23, 2008 9:20 pm Post subject: Re: Identifying Orphan Subscriptions with MQ Pub/Sub Broker |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20700
Location: LI,NY
|
| battie wrote: |
It's difficult if you're using the default SYSTEM.JMS queues as all subscriptions share the same queue. The orphan can be identified by cross checking the RegistrationCorrellId value output from the amqspsd command with the correlation ids of the messages on the SYSTEM.JMS.ND.SUBSCRIBER.QUEUE that you're using. You'll then need to manually deregister the subscriber and remove the unwanted messages.
A better solution is to use a dynamic queue and have one queue per subscriber. This can be either set on the URI or by setting the subscriber queue to SYSTEM.JMS.ND.* using the JMSAdmin tool. |
Note that you need to do this at subscription time and that is is part of your subscription topic. As such subscription topic and publication topic rarely match each other even if the topic string is the same. That's because the subscription queue is different.
Have fun 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
