Posted: Wed Mar 10, 2010 6:32 pm Post subject: MQ 7.0.1 Trigger on Depth issue
Yatiri
Joined: 11 Nov 2008 Posts: 610
Hi Guys,
MQ 7.0.1 on AIX 6.1.
I am trying to setup trigger an application to read the msgs off of the queue when the depth reaches certain count. The triggering is working on Every and First.
When I set the trigger with Depth and a depth count of 10 on the queue, the application is triggered for the very first time but the trigger is again resetting to "off"/notrigger on the queue and it never goes to "ON"/Trigger state on the queue. I dont see any error in the runmqtrm command output file.
Posted: Wed Mar 10, 2010 6:47 pm Post subject: Re: MQ 7.0.1 Trigger on Depth issue
Poobah
Joined: 15 May 2001 Posts: 7722
Sam Uppu wrote:
When I set the trigger with Depth and a depth count of 10 on the queue, the application is triggered for the very first time but the trigger is again resetting to "off"/notrigger on the queue and it never goes to "ON"/Trigger state on the queue.
Working as designed. Read about Depth Triggering in the manual. You have to reenable a Depth Trigger yourself each time. _________________ Peter Potkay
Keep Calm and MQ On
Posted: Wed Mar 10, 2010 7:49 pm Post subject: Re: MQ 7.0.1 Trigger on Depth issue
Yatiri
Joined: 11 Nov 2008 Posts: 610
PeterPotkay wrote:
Sam Uppu wrote:
When I set the trigger with Depth and a depth count of 10 on the queue, the application is triggered for the very first time but the trigger is again resetting to "off"/notrigger on the queue and it never goes to "ON"/Trigger state on the queue.
Working as designed. Read about Depth Triggering in the manual. You have to reenable a Depth Trigger yourself each time.
Thanks Peter.
Question:
When we run the trigger monitor in the background, we can go with below options:
1.) nohup runmqtrm -m <QMgr> -n <Initiation queue> > output file &
We can see all the errors associated with runmqtrm in the output file. We need to add the above syntax for the server startup scripts runmqtrm to come up automatically when the server is rebooted.
In this case, we no need to add it to the server startup scripts as this is controlled by Qmgr startup. If we define the Trigger monitor as a service and if there are any issues with trigger monitor where these errors are written or found?. In the Qmgr's AMQ* errors?.
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