| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| PUB SUB SYSTEM.MANAGED.DURABLE QUEUE |
« View previous topic :: View next topic » |
| Author |
Message
|
| mpong |
 Posted: Tue Jul 05, 2016 8:20 am Post subject: PUB SUB SYSTEM.MANAGED.DURABLE QUEUE |
 |
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
Hello All,
Msg is published to TOPIC and there is a .net client which is subscribed to it.
.net client is using the below property
<add name="TransportMode" value="managed" />
<add name="Durability" value="durable" />
<add name="NoOfMessage" value="500" />
When they are connected to qmgr, I could see them in the subscriptions.
I see the destination class is Managed and Destination name is [b]SYSTEM.MANAGED.DURABLE.573F66C8202C000D[/b]
Will the queue depth be increasing when they are not consuming the msg. In that case I am thinking of having alerting mechanism when depth is going beyond particular no. Please suggest. |
|
| Back to top |
|
 |
| hughson |
| Posted: Wed Jul 06, 2016 3:45 pm Post subject: Re: PUB SUB SYSTEM.MANAGED.DURABLE QUEUE |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| mpong wrote: |
| I see the destination class is Managed and Destination name is SYSTEM.MANAGED.DURABLE.573F66C8202C000D |
That seems correct given that the .net client subscribed with
| .NET Client property wrote: |
| <add name="TransportMode" value="managed" /> |
Any managed subscription is given a queue with a name beginning with SYSTEM.MANAGED and then either DURABLE or NDURABLE based on the durability of their subscription.
| mpong wrote: |
| Will the queue depth be increasing when they are not consuming the msg. |
Yes. That is the way a durable subscription works. Even when the application is not connected and is therefore not consuming messages from the managed subscription queue, messages will continue to be delivered to that queue.
Use of a DURABLE subscription and this behaviour is important if the application doesn't want to have any gaps in the stream of messages being published. If the application doesn't mind having gaps, and only needs to get messages when it is connected, then it should be a non-durable subscription instead.
| mpong wrote: |
| In that case I am thinking of having alerting mechanism when depth is going beyond particular no. |
This is a valid consideration, just as you would with other application queues. What will you do when you receive the alert that says the depth has gone beyond the number in question?
How to get alerts for managed queues
To get alerts for a certain queue depth, you need to use Queue Depth High events. Normally you would set the values for QDEPTHHI, QDEPTHLO and MAXDEPTH on your queue definition and then enable QDPHIEV on the queue and PERFMEV on the queue manager and you're off and running. (Read SHARE Presentation: Monitoring and Auditing WebSphere MQ for more information).
Managed queues are created based off a model queue. By default the model queues are SYSTEM.DURABLE.MODEL.QUEUE and SYSTEM.NDURABLE.MODEL.QUEUE. So to have new subscriptions automatically have Queue Depth Events turned on, you have to make changes to these model queues.
If you don't want to make the change to every single subscriber, which is what would happen if you alter those queues used by default, then you can change the model queue being used on a per TOPIC object basis by creating other model queues and naming them in the MDURMDL and MNDURMDL fields of the TOPIC object. Then you can enable Queue Depth Events only on certain subscribers, depending on which topic they are subscribing to.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| jasonn |
| Posted: Thu Dec 22, 2022 2:16 am Post subject: Re: PUB SUB SYSTEM.MANAGED.DURABLE QUEUE |
|
|
Newbie
Joined: 22 Dec 2022
Posts: 6
|
| mpong wrote: |
Hello All,
Msg is published to TOPIC and there is a .net client which is subscribed to it.
.net client is using the below property
<add name="TransportMode" value="managed" />
<add name="Durability" value="durable" />
<add name="NoOfMessage" value="500" />
When they are connected to qmgr, I could see them in the subscriptions.
I see the destination class is Managed and Destination name is SYSTEM.MANAGED.DURABLE.573F66C8202C000D
Will the queue depth be increasing when they are not consuming the msg. In that case I am thinking of having alerting mechanism when depth is going beyond particular no. Please suggest. |
Yes, the queue depth will increase when the messages are not being consumed, and you should consider setting up an alerting mechanism to detect when the queue depth exceeds a certain threshold. This can be done in your monitoring and alerting system, or you could use the WebSphere MQ client-side event monitoring feature. |
|
| 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
|
|
|
|
