| Author |
Message
|
| mqjeff |
 Posted: Fri Mar 27, 2009 10:26 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The intent of delaying messages in this scenario is to process "duplicate" messages later.
If you delay *all* messages by the same time period, then you have merely delayed the problem rather than solved it.
Otherwise, constantly asking the qmgr for the Oldest Message on the queue is going to be fairly inefficient.
One might as well just only get one message every 15 seconds. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Mar 27, 2009 10:49 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I read queuetips posts again, and I guess I'm not 100% clear on his requirements as it relates to the duplicate messages. The original question did just say how to delay a message. I assumed any and all messages on the queue.
Even if there was a way to tag an individual message that was a duplicate as dont open for 15 seconds, how would you know your messages was a duplicate as you were creating it? And if you somehow did know it was a duplicate as you were creating it, you could just delay the MQPUT for that duplicate by 15.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mq_developer |
| Posted: Sat Mar 28, 2009 9:11 am Post subject: |
|
|
Voyager
Joined: 18 Feb 2002
Posts: 82
|
I didn't read through whole length of posts and replies - if i hear you right , you dont want to "deliver" msgs to consuming application until 15 seconds elapse. (For whatever reasons / logic / requirement reason you need to do this).
This is what i would propose , code this requirement into to 'sending' application make the commit interval set to 15 seconds so dont commit until the period elapse or whatever you would do.
Rather trying to solve it in middleware layer may not be a good solution. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Mar 28, 2009 2:53 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| mq_developer wrote: |
| I didn't read through whole length of posts and replies... |
I'm sorry that this topic has soooo many posts. If you HAD read them, you would have learened your suggestion has alrerady been offered and deemed not practical given the requirements.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Mar 28, 2009 3:02 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I didn't read through whole length of posts and replies... |
Did we waste our time replying?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Nov 29, 2023 2:41 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Now we have delivery delay in MQ....
Is there a free MQ testing tool that support delivery delay?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
