|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
PUT disabling a queue using Microsoft Queue COM object |
« View previous topic :: View next topic » |
Author |
Message
|
mikehkk |
Posted: Thu Aug 01, 2002 2:04 pm Post subject: PUT disabling a queue using Microsoft Queue COM object |
|
|
Apprentice
Joined: 29 Jul 2002 Posts: 25
|
I'm working with a clustered queue implemented on several machines/queue managers across a network. In a certain scenario, I need to PUT-disable invidual queues on specific machine(s). When this occurs, I need for the correct round robining of incoming messages to continue correctly amongst the remaining PUT-enabled clustered queues.
When I try this on a queue using MS Queue COM object, it will correctly PUT-disable the queue. However, at least one of the channels in the cluster is not getting notified of this change: the cluster round robining mechanism still recognizes the PUT-disabled queue as a valid destination and attempts to deliver messages.
If I examine the queue via MQExplorer at this point, the InhibitPut property is correctly configured 'True'. I noticed too that if I select the 'Refresh' option a few times on the queue, this seems to finally propogate the its new state across the cluster: round robining of messages are correctly diverted to PUT-enabled queues at that point.
Do I somehow need to execute an explicit REFRESH command of some kind? On the cluster? The Queue Manager? In the COM objects documentation, there are no .Refresh() methods listed for QM or queue objects. If this needs to be done can you do via MSBag object? Or the ADSI interface? Could someone send me a solution?? Really appreciate it. Love to any and everyone's thoughts. Thanks. |
|
Back to top |
|
 |
nimconsult |
Posted: Thu Aug 01, 2002 10:17 pm Post subject: |
|
|
 Master
Joined: 22 May 2002 Posts: 268 Location: NIMCONSULT - Belgium
|
There is a similar post on
http://www.mqseries.net/phpBB2/viewtopic.php?t=4498
No you do not need to do some sort of refresh of the cluster. The information propagates automatically to the cluster, but it may take some time (seconds). This is not an issue however, because the messages that reach the queue manager where the queue is disabled will be redispatched to other available instances of the queue in the cluster (if any). If no available instance of the queue exists in the cluster, the messages end up in the dead-letter queue. _________________ Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
Back to top |
|
 |
jc_squire |
Posted: Mon Aug 05, 2002 2:48 pm Post subject: |
|
|
 Centurion
Joined: 14 Apr 2002 Posts: 105 Location: New Zealand
|
If the symptoms persist you could have a problem with replication of cluster info throughout the repositories in your cluster.
As a starting point you can look at: What version of MQ are you running? Does this only happen on a specific server or does it affect all your servers? How many full repositories do you have? Are there any network connectivity issues between hosts at the time when this occurs e.g. chls retrying ?
Regards _________________ J C Squire
IBM Certified Specialist - MQSeries |
|
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
|
|
|
|