Graham,
Did you check the TriggerInterval value of the QM? It won't tell why
these messages are stacking up to begin with (my guess is that the app is
triggered, but bombs sometimes before it ever even opens the queue), but it
will allow this app to be triggered without you intervening once the
interval passes and another message lands.
Peter Potkay
IBM MQSeries Certified Specialist, Developer
[EMAIL PROTECTED]
X 77906
-----Original Message-----
From: Miller, Dennis [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 28, 2002 3:37 PM
To: [EMAIL PROTECTED]
Subject: Re: messages pile up on a triggered queue
There I go again, making brash assumptions. But my reply still
might be some insights. I proposed: "The root of the problem is a triggered
application that doesn't completely empty the queue." I most often see that
with trigtype=every, but I suppose it could be true with a trigtype=first,
too.
I find this statement interesting:
> I process the messages by switching the trigger on the queue off
and then
> on.
With trigtype=every, that generates a trigger if the queue depth >0. With
trigtype=first, there is an additional condition that no program has the
queue open. That leads me to believe the triggered program has closed the
queue, but then I reach a contradiction, because with trigtype=first, the
close causes a re-trigger on its own. Sorry I cannot shed more light.
> -----Original Message-----
> From: Graham Lekota [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 26, 2002 1:00 AM
> To: [EMAIL PROTECTED]
> Subject: Re: messages pile up on a triggered queue
>
> Dennis,
> I am using trigtype=first.
>
> -------------------------------------------
> Graham Lekota(Liberty Group)
> IBM Certified Specialist, WebsphereMQ
> +27 83 327 3619 / +27 11 408 4683
> [EMAIL PROTECTED]
> *******************************************
> Reputation is what people think you are,
> Personality is what you seem to be,
> Character is what you really are.
>
>
>
>
>
> -----Original Message-----
> From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Miller,
> Dennis
> Sent: Friday, July 26, 2002 5:13 AM
> To: [EMAIL PROTECTED]
> Subject: Re: messages pile up on a triggered queue
>
>
> That's probably a queue backlog caused by the incorrect use of
> trigtype=every. In fact, I'm pretty sure you are using trigtype=every,
> otherwise turning the switching trigger off/on would not have an effect
> while the trigger monitor is running. The assumption that there is a
> corresponding trigger for every message is false. When there are fewer
> triggers than messages, then the pile-up occurs.
>
> The root of the problem is a triggered application that doesn't completely
> empty the queue. Even if you use trigtype=every, you must design your
> application to empty the queue or you risk the backlog you describe. After
> re-writing your program to empty the queue, then trigtype=every will
> likely
> be unneccessary overhead because a few instances of the application will
> read more than one message, but most of them will just find the queue
> empty.
> My advice is to nix the trigtype=every thing cause it doesn't do what you
> want, anyway.
>
> > -----Original Message-----
> > From: Graham Lekota [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, July 25, 2002 12:08 AM
> > To: [EMAIL PROTECTED]
> > Subject: messages pile up on a triggered queue
> >
> > I have a triggered queue on a solaris 5.6 machine(MQ ver 5.1, c trigger
> > monitor), the queue sometimes pile up with messages even though the
> > trigger
> > monitor is still running.
> > I process the messages by switching the trigger on the queue off and
> then
> > on.
> >
> > Does anyone know what could cause this. I have a similar server that
> runs
> > fine with the same infrastructure.
> >
> > Thanks in advance.
> > -------------------------------------------
> > Graham Lekota(Liberty Group)
> > IBM Certified Specialist, WebsphereMQ
> > +27 83 327 3619 / +27 11 408 4683
> > [EMAIL PROTECTED]
> > *******************************************
> > Wheresoever you go, go with all your heart.
> > --Confucius
> >
> >
> >
> >
> >
> > *******************************************************************
> >
> > This message may contain information which is confidential and subject
> to
> > legal privilege. If you are not the intended recipient, you may not
> > peruse, use, disseminate, distribute or copy this message. If you have
> > received this message in error, please notify the sender immediately by
> > email, facsimile or telephone and return and/or destroy the original
> > message.
> >
> > *******************************************************************
> >
> > 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
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
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If
you are not the intended recipient, please notify the sender
immediately by return email and delete this communication and destroy all copies.
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
