Hi Tim, As Jim said it may not be the TRIGGERINTERVAL that is generating the extra messages. I would look at the behaviour of your app. For instance, under Triggering condition 12, in notes b & c, it says that if your GET request is backed out "before" closing the input queue, a trigger message will be generated... You should check the backoutcount of the message in order to prevent such a loop.
What is the value of your TRIGGERINTERVAL? If it is very low it might act like trig type EVERY although the queue is defined as trig type FIRST. Best regards, Ruzi --- Jim Ford <[EMAIL PROTECTED]> wrote: > How do you know that the TRIGGERINTERVAL is > generating the extra > trigger messages? The way TRIGGERINTERVAL works is > that an 'extra' > trigger message is generated if: > > IPPROCS is 0 > CURDEPTH of the queue is > 0 > A new message arrives on the queue > More than TRIGGERINTERVAL msec has elapsed > since the last > trigger message was created for the queue > > At least two of those shouldn't be true in your > case. > > > > > > 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> > > > 03/03/2003 07:48 > PM > 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 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
