| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQGet node with get-inhibited queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| vmcgloin |
 Posted: Tue Dec 29, 2009 6:54 am Post subject: MQGet node with get-inhibited queue |
 |
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
Can anyone please tell me how they expect the MQGet node to behave when its queue is get inhibited (or rather after it is enabled again)?
What I had intended to achieve was to cause a timeout by get inhibiting the queue, waiting for the wait interval of the node to pass and the timeout behaviour to occur, then renabling the queue and see the orphaned reply message waiting on the queue.
What I actually see happen (using 6.1.0.4) is that the timeout does not happen, then when the queue is re-enabled the MQGet node processing continues as normal, i.e. the get does not start until the queue is get-allowed. Apologies if I have got 'mince-pie brain' but is that what you would have expected? I can't find documentation on the subject.
Thanks and Seasons Greetings,
Vicky |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Dec 29, 2009 7:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'd expect the MQGet node to immediately return with a non-zero MQRC if the queue is already get-disabled when the node is invoked.
I do not think the behavior of the MQGet node will differ from the behavior of a regular MQGET verb when it comes to GET_WITH_WAIT. I do not believe that get-inhibiting the queue will cause a pending GET to fail - but the MQ APR or APG should be explicit on that. |
|
| Back to top |
|
|
| zonko |
| Posted: Tue Dec 29, 2009 11:39 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
| Quote: |
| get-inhibiting the queue will cause a pending GET to fail |
it does
this is one of the ways to stop a trigger monitor, by get-disabling the init queue |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Dec 29, 2009 11:59 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Thanks for the replies. The queue was already get inhibited before the node (and flow) was invoked.
From the info center:
| Quote: |
If the state of the queue or the queue manager changes before the wait interval expires, the following actions occur:
...
If the attributes of the queue (or a queue to which the queue name resolves) are changed so that get requests are now inhibited, the wait is canceled and the MQGET call completes with the MQRC_GET_INHIBITED reason code. |
This is what I expected, but not what I saw happening. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 30, 2009 6:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If there's a discrepancy between product documentation & behaviour, then it's PMR time. At least the documentation needs to be updated...!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
