| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Identify the orphaned subscriptions |
« View previous topic :: View next topic » |
| Author |
Message
|
| sdrao |
 Posted: Wed Nov 10, 2004 7:44 am Post subject: Identify the orphaned subscriptions |
 |
|
Newbie
Joined: 10 Nov 2004
Posts: 2
|
All,
We have a scenario where the clients that register for Subscriptions can terminate ungracefully resulting in orphaned subscriptions. We find that in such a scenario the subcription Qs remain active for this subscriptions. Any publisher that publishes on this topic from now will result in messages being put into the SubscriberQ with no client processing the message. This results in a large number of messages in the Q which causes the MQ server slowdown after some time and in some case the MQ becomes inaccessible.
The Question:
1. Is there a way to identify the list of such orphaned subscription that have this subscriptionQs ( manual, programmatic, configuration). The idea is to idenitfy and deRegister these orphaned subscriptions manual or scheduled manner so that the subscriberQs get deleted.
Thanks
Sudesh
_________________
Sudesh |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Nov 10, 2004 8:08 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I don't know of a way to know that a subscriber is orphaned. However, there are some parameters that are kept for a durable subscriber vs. a non-durable subscriber. I'm not at my desk, so I can't remember what they are. You might also want to look at the Using Java cleanup script (see my other append). |
|
| Back to top |
|
|
| sdrao |
| Posted: Wed Nov 10, 2004 8:43 am Post subject: |
|
|
Newbie
Joined: 10 Nov 2004
Posts: 2
|
bower5932,
Thanks for your response. The 'Using Java' talks about a utility that is run in the background which does the cleanup on behalf of the 'MQ'. But, we see that the subsriber Qs are still active and they have queues after a long time and the utility did not do any cleanup.
What we are looking for is that in an instance when the 'Utility' is unable to do the clean, is there a way we can do 'UnSubsribe' selectively by identifying such orphaned subsription so that the Q does grow indefinitely to max and over-stress the broker.
I am not sure I understand the parameters that you refer to, please let me know the details.
Thanks
Sudesh
_________________
Sudesh |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 10, 2004 8:58 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Are you sure that your subscribers are orphaned and not durable subscribers that aren't currently active? If they are durable and not active, they will still get all of the publishes.
If they are non-durable and don't deregister, the cleanup script should remove them. There was a problem in this area that was fixed after CSD4. What version of the code are you running? What broker are you running?
As far as the parameters, they are a couple of fields (I'll post names later) that show up in a durable subscriber and not in a non-durable subscriber. If they show up when you look at registrations, it lets you know which type of subscriber you have.
You can also unsubscribe selectively. You can use DumpBroker and UnSubscribe from:
http://www.developer.ibm.com/tech/sampmq.html
You'll need to edit the DumpBroker output to only have the subscribers you want deregistered and then pipe it into UnSubscribe. |
|
| 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
|
|
|
|
