| Author |
Message
|
| BMT |
 Posted: Fri Apr 22, 2016 5:15 am Post subject: dmpmqmsg -T (seconds) |
 |
|
Newbie
Joined: 12 Sep 2012
Posts: 4
|
Hey
I need to monitor a Queue and move messages older than 10 seconds to another local Queue.
dmpmqmsg seems to only be able to handle DD:HH:MM and no seconds, thus making life a little more interesting for me at the moment.
Any ideas or advise would be appreciated.
BMT |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Apr 22, 2016 5:30 am Post subject: Re: dmpmqmsg -T (seconds) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| BMT wrote: |
| I need to monitor a Queue and move messages older than 10 seconds to another local Queue. |
Why? If the messages are not needed after 10 seconds why not just set the expiry?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| BMT |
| Posted: Mon Jun 06, 2016 12:50 am Post subject: |
|
|
Newbie
Joined: 12 Sep 2012
Posts: 4
|
| The need to move the messages after 10 seconds is purely due to crappy programming from an application p.o.v. The app drops a message on the queue and the message should immediately be processed to a 3rd party Q-manager sitting on an external site. If this does not happen within 10 seconds the app will need to be updated thus the message needs to be moved to a different queue which will be monitored by the app to process these messages asap. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 06, 2016 3:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The app can set expiry options to get a report including the full message data. It can then do what it needs to do.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| boos |
| Posted: Tue Aug 16, 2016 4:27 am Post subject: |
|
|
Apprentice
Joined: 27 Jan 2004
Posts: 34
Location: Netherlands
|
| Quote: |
| can set expiry options to get a report including the full message data. It can then do what it needs to do |
True for the functionality of it. But not true for the exact 10sec expiry. The report is only produced when the message expires. But the expiration is only checked if the queue is accessed. Which may not be in the same second the message expires. So you don't exactly know when the report/message wil appear on the second queue (only that it will not appear within the 10 seconds) |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Aug 16, 2016 11:39 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
So what is the plan ? Are you going to run dmpmqmsg every 10 seconds, over and over and over again ? That strikes me as woefully inefficient. It certainly seems to me as though this is trying to get round poor design in the application.
The idea being the -T parameter was so that someone could look for 'old' messages and clean-up their queues. When I wrote it I never thought that someone would thing of 10 seconds as old. Just goes to show that whenever you put a limit in software, someone will hit it  Perhaps I should consider adding seconds to our QLOAD product.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 16, 2016 4:45 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
While you're there, how about microseconds?? 
_________________
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 |
|
|
| PaulClarke |
| Posted: Tue Aug 16, 2016 5:44 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Ha! Surely that would just show you up as impatient 
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
|
|
