| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| triggering type: FIRST vs. EVERY |
« View previous topic :: View next topic » |
| Author |
Message
|
| AlexeiSkate |
 Posted: Wed Mar 12, 2003 11:19 am Post subject: triggering type: FIRST vs. EVERY |
 |
|
Centurion
Joined: 10 Apr 2002
Posts: 123
|
Hi,
We have a client that will run a batch program to dump a bunch of messages onto a triggered queue. I have a triggered GET application that reads one message off the queue each time it's executed.
Should I set the trigger type to FIRST or EVERY? Suppose the batch process dumps 3 messages onto my triggered queue, will either trigger type ensure that all of the messages in the queue will be processed? Are there pros or cons with using either type? Thanks in advance. |
|
| Back to top |
|
 |
| lillo |
| Posted: Wed Mar 12, 2003 11:35 pm Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
A think this is a MQ question, no WMQI question. Anyway, it depends on your application.
The trigger EVERY will try to run your application every time a new message arrive which satisfy the trigger conditions. If you open the queue in the exclusive mode you will have only one instead of your application each time.
The trigger FIRST will run your application only the first time a new message arrive which satisfy the trigger conditions. Once the program execute the trigger switch off and in order to run again the program you must turn it on, manually or automatically.
I´m sure other people could add their suggestion here.
Cheers,
_________________
Lillo
IBM Certified Specialist - WebSphere MQ
Last edited by lillo on Thu Mar 13, 2003 2:21 am; edited 1 time in total |
|
| Back to top |
|
|
| bob_buxton |
| Posted: Thu Mar 13, 2003 1:24 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
I would reccomend against using trigger type EVERY, you should always design a triggered application to read all of the messages available off the queue.
Trigger type EVERY introduces extra overhead with the need for MQ to generate the trigger message, for the trigger monitor to process the message & invoke your application and for your application to repeat its initialization including opening queues and other resources for each message. Also with trigger EVERY you can't guarantee there will be an application triggered for every message on the queue - only a single message is triggered when the trigger monitor first starts up and no trigger messages are generated if the application rolls back the message onto the queue.
_________________
Bob Buxton
Ex-Websphere MQ Development |
|
| Back to top |
|
|
| rajpath |
| Posted: Thu Mar 13, 2003 2:56 am Post subject: First or Every |
|
|
Novice
Joined: 12 Jun 2002
Posts: 12
Location: Mumbai
|
Hello
If ur getting the message I guess FIRST will be appropraite cause everytime the queue depth will be 0.
But getter application has to take care about backout and commits of messages.
Else EVERY is the best option.
_________________
Raj
Software Engineer
Mahindra Consulting Ltd
Mumbai-101 India |
|
| 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
|
|
|
|
