| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Question in regards to IBM Web Sphere MQ Series and trigger |
« View previous topic :: View next topic » |
| Author |
Message
|
| tomas rivas |
 Posted: Thu Oct 19, 2006 10:41 am Post subject: Question in regards to IBM Web Sphere MQ Series and trigger |
 |
|
Newbie
Joined: 19 Oct 2006
Posts: 1
|
For some time we have been using MQ series on the iSeries platform and recently we have run into an issue that I cannot find an answer for it. The scenario is the following,
We have configured 3 local queues with trigger option enabled (EVERY), 3 processes and we have set the 3 queues to pint to a single initiation queue. The main purpose of this configuration is to have a central point for monitoring this trigger and initiate jobs on another platform (Windows).
Case 1: Normal behavior –
If the Windows service that acts as the trigger monitor program is started it does not matter the number of entries we place on any of the three queues, all the trigger are generated and all the messages are processed by the trigger monitor program.
Case 2: Inexplicable behavior –
If the Windows service (trigger monitor) is stopped and we write several entries to these queues, the triggers are not shown on the initiation (normal b/c no monitor program is connected). As soon as the monitor program starts only 2 of the 10 entries are created on the initiation queue.
Any idea or explanation for this?
Thanks, |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Thu Oct 19, 2006 11:40 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Sounds about right to me.
I believe triggering on EVERY will not generate a trigger message for every message on the queue at trigger monitor startup. (I am not sure I would want it too anyway).
Personally I always try to steer clear of trigger type of EVERY because it is rarely needed. Trigger type of FIRST usually suffices for about 90% of triggering in my experience.
IMHO The most important part of triggering is how the triggered application processes the queue. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Oct 19, 2006 11:03 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
check the trigger conditions in the manual (quite a few pages in the application programmers guide)
if a trigger monitor is stopped then no trigger message is created in the initiationqueue. why should mq create these when no trigger monitor is present to process them?
when a trigger monitor is started (or better, when a qlocal is opened) mq checks if that qlocal is used as an initiationqueue in other qlocals and - if so - checks if trigger conditions met. but - afaik - for a queue with trigger every only one trigger message is created in that case.
_________________
Regards, Butcher |
|
| 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
|
|
|
|
