MQSeries.net :: View topic - Client Trigger Monitor picking up "ghost" trigger messages?

PeterPotkay · Posted: Mon Jan 28, 2002 9:11 am Post subject:

Q1 and Q2 are both triggered on Every with an initiation queue of INIT.QUEUE. Q1 has a process that will start the calculator, Q2 has a process that will start a little VB app that displays the current time.

At the start of this test (testing automatic startup of the client trigger monitor), both queues have a depth of 10, and the initiation queue has a depth of zero. I then start the client trigger monitor on the Client machine (WIN2000 laptop). I get one instance of the calculator start up, and then when I close it, one VB clock pops up. But there were no messages in the init queue! Why/How did the Trigger Monitor start these apps?

I then CTRL-C the trigger monitor to end it. IPROCS is 1 on the init queue for about 10 seconds after I kill the trigger monitor. If I start another Trigger monitor while IPROCS>0 on the init queue, the trigger monitor starts up ok, but no apps get started (this makes sense, as there are no messages on the init queue). BUT, if I kill all trigger monitors watching this init queue and wait till the IPROCS goes to zero (about 10-15 seconds), and then restart the trigger monitor, the 2 apps start up again!

What is going on? During this entire test, no new messages were put to either triggered queue and the queue manager was up and running the whole time.

_________________
Peter Potkay
Keep Calm and MQ On