| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trigger Event not occuring |
« View previous topic :: View next topic » |
| Author |
Message
|
| raman |
 Posted: Mon May 20, 2002 4:56 pm Post subject: Trigger Event not occuring |
 |
|
Novice
Joined: 15 May 2002
Posts: 13
|
Hi,
I have done the following steps for the triggering to work. But the triggering event is not occuring.
Steps:
1. Created a new local queue to use it as a initiation queue.
2. Created a process definition and specified the name of the .bat file.
3. Changed my application queue triggering properties.
Trigger Control: ON
Trigger Type: Every
Trigger Depth: 1
Trigger Message Priority: 0
Name of my Initiation Queue
Name of the process I have created.
4. Stoped and started the channel thru with I am putting a message on the application queue.
When I put a message on my application queue, I don't see any trigger message on the initiaiton queue.
I am not running any trigger monitor. Is that a problem? Because at this time I just want to make sure trigger event occurs and QM puts a message on the initiation queue.
am I misssing any steps?
Thanks
raman. |
|
| Back to top |
|
 |
| kingsley |
| Posted: Mon May 20, 2002 6:04 pm Post subject: Trigger monitor , a must |
|
|
Disciple
Joined: 30 Sep 2001
Posts: 175
Location: Hursley
|
Hi,
You have start the trigger monitor with the name of initiation queue and the Queuemanager.
It is the trigger monitor that actually starts the application which we want to trigger
Please check |
|
| Back to top |
|
|
| raman |
| Posted: Mon May 20, 2002 7:25 pm Post subject: |
|
|
Novice
Joined: 15 May 2002
Posts: 13
|
Hi kalyan,
Thanks for the reply.
I am using MQSeries Explorer to see if there is any message on initiation queue. Even without the trigger monitor, whenever an application queue receives a message the trigger event must be occured and the queue manager must put a message on the initiation queue. Do I need a trigger monitor for this to occur? or am I missing any thing in between?
Thanks
raman. |
|
| Back to top |
|
|
| bduncan |
| Posted: Mon May 20, 2002 9:03 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Raman,
If your triggered queue and your initiation queue are configured properly you should see the trigger messages land on the initiation queue whether or not the trigger monitor is actually running. So the fact that nothing is landing on the initiation queue probably means your triggered queue isn't configured properly. From your description everything looks okay. However, you might want to simplify the situation some by changing from trigger type EVERY to trigger type FIRST. Then ensure that the queue depth on your triggered queue is 0, and then add a single message. Use the amqsput sample program to put the message to the queue. Again, this decreases the number of unknown factors in the problem. Now when the depth of the triggered queue goes from 0 to 1, you should see a single message appear on the initiation queue. If you don't see anything, check the number of IPPROCS and OPPROCS on the initiation queue. If either of these are nonzero, it means that something is listening to (has opened) the initiation queue, and it is likely this application that is picking up the message before you have a chance to see it arrive on the initiation queue...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Mon May 20, 2002 10:23 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
| bduncan wrote: |
Raman,
If your triggered queue and your initiation queue are configured properly you should see the trigger messages land on the initiation queue whether or not the trigger monitor is actually running. So the fact that nothing is landing on the initiation queue probably means your triggered queue isn't configured properly. From your description everything looks okay. However, you might want to simplify the situation some by changing from trigger type EVERY to trigger type FIRST. Then ensure that the queue depth on your triggered queue is 0, and then add a single message. Use the amqsput sample program to put the message to the queue. Again, this decreases the number of unknown factors in the problem. Now when the depth of the triggered queue goes from 0 to 1, you should see a single message appear on the initiation queue. If you don't see anything, check the number of IPPROCS and OPPROCS on the initiation queue. If either of these are nonzero, it means that something is listening to (has opened) the initiation queue, and it is likely this application that is picking up the message before you have a chance to see it arrive on the initiation queue... |
OK guys, I had a couple of days of vacation in the desert and my brains may be a bit dry (we had 107 degrees...), but isn't one of the trigger conditions, that somebody is actually watching the inititation queue (MQOPEN for input)? Yes, I think that's what it is. The queue manager is saving the effort to generate trigger messages if it detects that nobody cares. Or do I have to go back to class again!? 
Awaiting the foul tomatoes,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 21, 2002 4:05 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
Stefan,
You are correct. There are something like 13 conditions that need to be met in order for the QM to generate a trigger message to the init queue. One of those conditions is that the init queue has an IPROCS count greater than 0. (Which desert by the way?)
Raman,
If you want to "trick" the QM, you can have a little dummy app that does a Get With Wait on the Init queue specifying a CorrelId that you know won't appear in that queue. Since the dummy app increases the IPROCS from 0 to 1, but will never actually return a message, you can trap your trigger messages to prove they are being created.
See the Application Programming Guide, Chapter 14, Section Conditions for a Trigger Event.
http://www-3.ibm.com/software/ts/mqseries/library/manualsa/csqzal05/csqzal05tfrm.htm
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue May 21, 2002 8:20 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Yes, well the desert didn't fry your brain Stefan, but apparently all the rain we've been getting has soaked mine... 
Remembering those 13 or so trigger conditions is like remembering all the constitutional amendments. You remember all the useful ones, freedom of speech, no unreasonable search and seizure (especially if you are O.J.), right to bear arms (useful if you are Robert Blake), no double jeopardy (good if you are either of those guys), and if you're poor like me, no excessive bail. 
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| jlamond |
| Posted: Tue May 28, 2002 7:17 am Post subject: Trigger monitor rules |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
Seam like some folk out there did forgot the nine (9) rules to produce trigger message.... One of them is thet the trigger monitor must run OR the INITQ must be open input by a process !
| raman wrote: |
Hi kalyan,
Thanks for the reply.
I am using MQSeries Explorer to see if there is any message on initiation queue. Even without the trigger monitor, whenever an application queue receives a message the trigger event must be occured and the queue manager must put a message on the initiation queue. Do I need a trigger monitor for this to occur? or am I missing any thing in between?
Thanks
raman. |
_________________
Jean-Marc |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
