| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| STOP TRIGGER PROCESS |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Thu Sep 25, 2003 12:06 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
Hmmm, I think I see why you did it this way.
So the app watches the INIT queue all the time, waiting for a trigger message, and as soon as it finds one, it then knows to go open the queue that made the QM create the trigger message in the first place?
It opens that triggered queue, reads all the messages, and then closes that triggered queue?
And all along, it never closes the Init queue? And never Disconnects from the QM?
If you could answer these questions when you get a chance, I'll be able to think about your problem correctly and see what we can come up with.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Thu Sep 25, 2003 2:10 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Peter
Exactly right. We use this method to perform lots of 'event' action, like issue a WTO when a message hits the DLQ (although we don't read the message in this case), is the text of a message as a WTO is a method we use to notify automation to do something. We also have an ECHO process that will send a message back to the replytoq so that our distributed folks can check out 'their' connections with us having to get involved.
You are correct in your assumption that we sit and hold the INITQ open for the entire time and that we pop an ECB to wake the subtask up when he has some work to do. I suspect that what is happening is that we don't close the 'application queue' right way in the subtask and that the subtask keeps this queue open (the subtasks get started at initiaion and remaining running until a shutdown is requested). As I understand it that would mean that a trigger message wouldn't get issued because we have something that has the queue open for input...even though the subtask has finished it's work for the time being.
I will verfiy this on Monday when I return to the office.
That would explain an awful lot! Thanks for the pointers |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 26, 2003 5:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Generally, if you're keeping a queue open all the time, you shouldn't be using triggers at all.
It's not clear what advantage you gain from the way you're doing things. Maybe you're keeping your processor and memory useage lower than you might if you were keeping all the particular queues you're interested in open with a Get with wait. But you're incurring extra overhead for having to repeatedly open and close queues every time you're interested in getting an application message. Whether this is cost effective or not is something you'll have to evaluate.
It sounds like you're trying to build a home grown application server. That's fine, but basing it on triggering is not the way I'd do it, myself. I'd write a threaded app that put listeners on application queues. As you've discovered, triggering conditions are complicated.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Mon Sep 29, 2003 10:52 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Peter
Yep, we were opening the queue and were leaving it open. That explains a great deal. Thanks for the pointers. 
Jeff
We don't issue an MQGET with wait for all the queues. The monitor uses the process name to determine what to do with the messages in any particular queue (make it a WTO), issue a notify message, send an email etc. The queue was being left open 'to save time' if the next time through the process was for the same queue. |
|
| Back to top |
|
|
| emileke |
| Posted: Wed Oct 01, 2003 11:34 pm Post subject: Stopping trigger process |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
| How do you gracefully end the trigger monitor process on AS400? |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
