| Author |
Message
|
| Alex87 |
 Posted: Wed Feb 19, 2014 9:51 pm Post subject: Intercepting message before it could be taken from queue |
 |
|
Newbie
Joined: 16 Aug 2011
Posts: 4
|
Hello!
Here is the goal of my efforts: in the test environment we're trying to tune up autotesting. The problem is that other applications are connected and reading messages from queues and we need to 'intercept' ant messages in their queues before they can read them. For a period of time (hour or maybe two) we need to prevent them from reading messages without causing any problems to them (like application errors/exceptions etc). I've tried couple solutions like calling MQGET with high frequency. It works, but it doesnt looks good.
Now i'm out of any ideas about doing it in the 'right' way and need some advices  |
|
| Back to top |
|
 |
| fatherjack |
| Posted: Thu Feb 20, 2014 3:09 am Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
If it's a test environment why don't you just stop the other applications and then you can browse away to your heart's content.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| Alex87 |
| Posted: Thu Feb 20, 2014 4:23 am Post subject: |
|
|
Newbie
Joined: 16 Aug 2011
Posts: 4
|
| Well. Some of our customers' IT staff might be a bit unhappy if they come to work at monday and see that couple of their apps (even in test environment) crashed. And since we can't affect quality of their apps, we need to find the way to work this way. And we can't force them to shut down their apps also. It's kinda pain, I know... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 20, 2014 5:17 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Exactly why do you want to suspend (delay, slow down) message consumers - in production or test? Just to be able to browse some messages before they are consumed?
WMQ is designed to deliver messages as quickly as the hardware and consumers can manage. WMQ is not designed to slow down this process. WMQ offers no tools for delaying messages - other than disabling MQGETs on a queue (definition).
_________________
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 |
|
|
| Alex87 |
| Posted: Thu Feb 20, 2014 7:04 am Post subject: |
|
|
Newbie
Joined: 16 Aug 2011
Posts: 4
|
| bruce2359 wrote: |
Exactly why do you want to suspend (delay, slow down) message consumers - in production or test? Just to be able to browse some messages before they are consumed?
|
Exactly.
It seems that we will end up with disabling customer's channels and will make them happy with fixing their errors and handling exceptions |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Feb 20, 2014 7:31 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| Alex87 wrote: |
| bruce2359 wrote: |
Exactly why do you want to suspend (delay, slow down) message consumers - in production or test? Just to be able to browse some messages before they are consumed?
|
Exactly.
It seems that we will end up with disabling customer's channels and will make them happy with fixing their errors and handling exceptions |
if their apps can't handle interruptions you have a bigger problem...
include interuptions, shutdowns, restarts in your acceptance criteria / tests, apps should be able to handle that without problems... 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 20, 2014 7:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you want to just SEE the messages, you can use any of various techniques to DUPLICATE them, rather than INTERCEPT them. |
|
| Back to top |
|
|
| Alex87 |
| Posted: Sun Feb 23, 2014 10:34 pm Post subject: |
|
|
Newbie
Joined: 16 Aug 2011
Posts: 4
|
| Well it would be way better to intercept them, because we need to put replies on some. But I will check duplicating messages, maybe it will be acceptable solution. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Mon Feb 24, 2014 5:00 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
If you really want to intercept them then this just sounds like you need to daisy chain your queues.
Instead the of the applications remote queue pointing to the 'correct' server queue point it at your intercept queue. You can then hold on to the message, reply if necessary or do whatever. When you've finished with it you then put it on the 'correct' server queue and let processing continue as normal. This is just a standard sort of workflow arrangement.
I agree with the other posters though that you need to be very careful you don't cause considerable annoyance with this. I can't imagine many application groups happy with the middle-ware administrators injecting an hour delay in their message traffic.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
|
|
