Timbo,
I think TriggerInterval operates regardless of the other conditions
necessary for triggering to occur. Anyway see excerpt below.
Regards
Tim A
Special case of trigger type FIRST
With trigger type FIRST, if there is already a message on the application
queue when another message arrives, the queue manager does not usually
create another trigger message. However, the application serving the queue
might not actually open the queue (for example, the application might end,
possibly because of a system problem). If an incorrect application name has
been put into the process definition object, the application serving the
queue will not pick up any of the messages. In these situations, if another
message arrives on the application queue, there is no server running to
process this message (and any other messages on the queue).
To deal with this, the queue manager creates another trigger message if
another message arrives on the application queue, but only if a predefined
time interval has elapsed since the queue manager created the last trigger
message for that queue. This time interval is defined in the queue manager
attribute TriggerInterval. Its default value is 999 999 999 milliseconds.
You should consider the following points when deciding on a value for the
trigger interval to be used in your application:
If TriggerInterval is set to a low value, trigger type FIRST might
behave like trigger type EVERY (this depends on the rate that
messages are being put onto the application queue, which in turn may
depend on other system activity). This is because, if the trigger
interval is very small, another trigger message is generated each
time a message is put onto the application queue, even though the
trigger type is FIRST, not EVERY. (Trigger type FIRST with a trigger
interval of zero is equivalent to trigger type EVERY.)
If a unit of work is backed out (see Trigger messages and units of
work) and the trigger interval has been set to a high value (or the
default value), one trigger message is generated when the unit of
work is backed out. However, if you have set the trigger interval to
a low value or to zero (causing trigger type FIRST to behave like
trigger type EVERY) many trigger messages can be generated. If the
unit of work is backed out, all the trigger messages are still made
available. The number of trigger messages generated depends on the
trigger interval, the maximum number being reached when trigger
interval has been set to zero.
Tim Clarke
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.AU> cc:
Sent by: MQSeries Subject: Triggerinterval firing when
queue is still open
List
<[EMAIL PROTECTED]
N.AC.AT>
04/03/2003 12:48
Please respond to
MQSeries List
I am have a queue with trigger FIRST and an application
that is doing a GET with a WAITINTERVAL of 5 minutes.
The application is staying running for hours keeping the
queue open, but the TRIGGERINTERVAL is still generating
extra trigger messages.
My understanding from the Appl. Prog. Guide (Chapter 14)
in "Conditions for a trigger event" point 11 is that
for a trigger message to be generated by the TRIGGERINTERVAL
conditions 2-10 (excl. 3) must be satisfied and condition 4
is that the queue must have an OpenInputCount of 0.
So, if the application still has the queue open, why are
these extra trigger messages being generated ?
*********************************************************************************
This email contains information confidential to AAMI Limited. If you are
not the intended recipient, you must not disclose or use the information in
it. If you have received this email by error, please notify us immediately
by return email, and delete this email and any attached documents.
AAMI Limited is not responsible for any changes made to a document other
than those made by AAMI Limited or for the effect of the changes on the
document meaning.
**********************************************************************************
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
