Posted: Thu Apr 12, 2012 10:41 am Post subject: Setting Queue property to FIFO doesn't work
Novice
Joined: 13 Feb 2012 Posts: 16
It's odd I have a queue with messages and the flow will process these messages in the order that they were received but now if a new message arrives onto that queue. It will be processed next as opposed to the messages on the queue already.
The message delivery sequence of the queue property is set to FIFO. I have the MQInput node set to browse only with a timeout of 5 minutes. This way every five minutes the flow will search through the queue to look for things. The request changes dynamically so in 5 minutes the criteria may match and the message may be found in the queue. But as new messages arrive on the queue, they trigger the flow to start and only processes the last message.
Posted: Thu Apr 12, 2012 11:02 am Post subject: Re: Setting Queue property to FIFO doesn't work
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
jim777 wrote:
How can I get a true FIFO system for the queue?
By not using browse. I imagine that (for one reason or another) the browse cursor's not at the top of the queue so doesn't find the earlier messages.
You mention a dynamic request - what is the criteria here? Why are you browsing these messages with an MQInput rather than an MQGet?
Perhaps with a little more detail we can suggest a way to outflank the problem. _________________ Honesty is the best policy.
Insanity is the best defence.
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