| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Inconsitent behavior of MQGet node |
« View previous topic :: View next topic » |
| Author |
Message
|
| sankritya |
 Posted: Thu Mar 20, 2008 2:41 am Post subject: Inconsitent behavior of MQGet node |
 |
|
Centurion
Joined: 14 Feb 2008
Posts: 100
|
Hi all,
I am using MQGETNODE and also checking its Browse only property.But i am facing some inconsistent behaviour of MQGET i.e. sometimes the message is read from the queue and some times it doesn't read from the specified queue(i.e. it comes out from no message teriminal),although there is message in the queue.Please help me to solve this problem.
I am using RFHutil for testing it. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 20, 2008 2:46 am Post subject: Re: Inconsitent behavior of MQGet node |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sankritya wrote: |
| sometimes the message is read from the queue and some times it doesn't read from the specified queue(i.e. it comes out from no message teriminal),although there is message in the queue. |
Do you have any match options set?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sankritya |
| Posted: Thu Mar 20, 2008 3:27 am Post subject: |
|
|
Centurion
Joined: 14 Feb 2008
Posts: 100
|
| Yes I am matching it with message ID but if I don't use the message ID option then also inconsistency persists. |
|
| Back to top |
|
|
| shalabh1976 |
| Posted: Sun Mar 23, 2008 8:16 am Post subject: |
|
|
Partisan
Joined: 18 Jul 2002
Posts: 381
Location: Gurgaon, India
|
Sankritya,
You have not specified whether you are using the MQGet in Browse mode or otherwise.
I triued your scenario and everything is fine if I do a proper Get.
However when I set the MQGet in Browse mode and run the whole flow in a loop using PROPAGATE I do see something funny.
What I see is this--->
Suppose you are using the MQGet node in Browse mode on Queue QA which has a queue depth of 2.
If you now enter this node 2 times (using a propagate from a previous Compute) the messages come out fine from the OUT terminal.
However if you enter this node anymore the control goes out from the No message terminal.
Hence your output is a function of the queue depth of the queue that MQGet is accessing.
I think this is not correct. Even if the queue depth is 1 and you use the browse option the control should pass from the out terminal for every pass through the node assuming all other conditins are met.
What made may be happening is that a BROWSE_NEXT might be happening on MQGet but since no messages are found it returns control to the No message terminal.
_________________
Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate |
|
| 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
|
|
|
|
