| Author |
Message
|
| jonesn |
 Posted: Tue Dec 18, 2007 7:26 am Post subject: amqspsd & durable subscriptions |
 |
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
Chaps,
I am fairly new to MQPubSub and have a simple question.
I want to confirm which subscribers in a PubSub broker are durable & which are not.
Am I correct in thinking that the output from amqspsd will include a SubscriptionName attribute for durable and this attribute is missing for non-durable?
Is this the only difference in the output of this command?
Thanks
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Dec 18, 2007 10:01 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| You do get a SubscriptionName for the durable subscribers. I'm not sure that I would base 'something' on this being the difference. What exactly are you trying to do? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Dec 18, 2007 10:14 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
All subscriptions are durable in the embedded broker (former MA0C support pack), the broker that amqspsd interrogates.
Only the JMS broker has a concept of non-durable subscriptions.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| jonesn |
| Posted: Wed Dec 19, 2007 12:31 am Post subject: |
|
|
Apprentice
Joined: 09 Jan 2002
Posts: 47
|
Responses to the two questions raised...
bower5932: I am trying to debug an application that the company I work for bought from a third party. The vendor are not being very cooperative when I ask questions about their code (I doubt they still have the messaging resources around). They claim that all their subscriptions are durable the output from amqspsd shows only two subscriptions with a SubscriptionName attribute. This suggests a mixture of durable & non-durable. Am I reading this correctly or is there something else to take into account?
Nigelg: I am confused by your statement. In this environment I have a single MQPubSub broker provided with MQ6.0.2.2 on AIX and amqspsd queries this. The application uses JMS to interface with this broker. What do you mean by the term JMS Broker?
Regards
_________________
---
Nick Jones
IBM Certified Solutions Expert (WebSphere MQ Integrator) |
|
| Back to top |
|
|
| markt |
| Posted: Wed Dec 19, 2007 1:11 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
There is no such thing as a "JMS Broker".
Possibly Nigel means the JMS API which permits both durable and non-durable subscriptions to be made. While the MQ pub/sub component only truly understands durable today, non-durable are "emulated" within the JMS API layer (and some corresponding cleanup code in the queue manager). |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Dec 19, 2007 4:18 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Thanks, that is what I meant...
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Dec 19, 2007 7:03 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| jonesn wrote: |
| I am trying to debug an application that the company I work for bought from a third party. The vendor are not being very cooperative when I ask questions about their code (I doubt they still have the messaging resources around). They claim that all their subscriptions are durable the output from amqspsd shows only two subscriptions with a SubscriptionName attribute. This suggests a mixture of durable & non-durable. Am I reading this correctly or is there something else to take into account? |
I would suggest that you shutdown their application and then look to see who is actually subscribed to the topic. The subscription of a durable subscriber 'hangs around' and if you end the application, the output of amqspsd should show them if they are durable. |
|
| Back to top |
|
|
|
|
