| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to insert delay in picking messages from queue (WMB 6.0) |
« View previous topic :: View next topic » |
| Author |
Message
|
| Shikha Gupta |
 Posted: Tue Jun 02, 2009 2:52 am Post subject: How to insert delay in picking messages from queue (WMB 6.0) |
 |
|
Apprentice
Joined: 18 May 2009
Posts: 27
|
Is there any way by which I can control the compute node to pick messages from an input queue after a specified delay time.
like 2nd message be picked up from the queue after n milliseconds.
some property to be set via ESQL programming? |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Tue Jun 02, 2009 2:55 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
u either need to user TimeOut nodes or an MQGET node to introduce delay..
but why do u want delay? what is the requirement ?
_________________
Cheers |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 02, 2009 2:55 am Post subject: Re: How to insert delay in picking messages from queue (WMB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Shikha Gupta wrote: |
| Is there any way by which I can control the compute node to pick messages from an input queue after a specified delay time. |
Your first problem is that the compute node doesn't pick messages up from an input queue at all, never mind after a delay.
| Shikha Gupta wrote: |
| like 2nd message be picked up from the queue after n milliseconds. |
If you want to process one message only after a second message has arrived, then use grouping.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jun 02, 2009 3:29 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Sounds like another bad design. Each message should initiate a message flow.
Each message should be self-contained and not reliant on the one following.
Grouped messages are possible but this sounds more like a case of using different queues and using the aggregate node to wait for one message on each queue before continuing the flow.
In almost every case where people talk about delaying message processing - they are not thinking the correct way about the design. You can't just wait a couple of seconds - apart from being wrong to stop a message flow, what happens if the message takes a couple of hours - the design must cope with all possibilities and be 100% robust under stress.
Many of these threads describe designs that would be, at best, highly fragile and unreliable. There is always a better way to do it. |
|
| 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
|
|
|
|
