| Author |
Message
|
| akm.mohan |
 Posted: Wed Dec 03, 2008 3:16 pm Post subject: trigger is not working |
 |
|
Apprentice
Joined: 07 Oct 2008
Posts: 41
|
Hi all,
100 msgs in the local queue, so i have setup the trigger properties like on, first trigger depth 1 process definition and intiation queue but still i am able to see all the messages in that queue. so could you please help me to figure out this problem.
Thanks,
Mohan, |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 03, 2008 3:39 pm Post subject: Re: trigger is not working |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| akm.mohan wrote: |
Hi all,
100 msgs in the local queue, so i have setup the trigger properties like on, first trigger depth 1 process definition and intiation queue but still i am able to see all the messages in that queue. so could you please help me to figure out this problem.
Thanks,
Mohan, |
Do you have a trigger monitor running? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| masteringmq |
| Posted: Wed Dec 03, 2008 5:14 pm Post subject: |
|
|
Master
Joined: 20 Oct 2008
Posts: 200
|
| runmqtrm -m <QueueManager> -q <InitiationQueue> |
|
| Back to top |
|
|
| zlj |
| Posted: Wed Dec 03, 2008 6:09 pm Post subject: |
|
|
Apprentice
Joined: 13 Nov 2008
Posts: 32
|
Set trigger type to "depth", trigger depth to 1?
Ensure you have trigger data and initQ already, if your initQ is not System.ChANNEL.INITQ, you need a monitor for initQ!
Regards! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 04, 2008 12:44 am Post subject: Re: trigger is not working |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akm.mohan wrote: |
could you please help me to figure out this problem.
|
If you have 100 messages in a queue setting a trigger to fire when the first one shows up is futile - the first message showed up 99 messages ago and you missed it.
Please read the documentation on triggering. And think about what you're doing. Not necessarially in that order.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zlj |
| Posted: Thu Dec 04, 2008 1:02 am Post subject: Re: trigger is not working |
|
|
Apprentice
Joined: 13 Nov 2008
Posts: 32
|
| Vitor wrote: |
| akm.mohan wrote: |
could you please help me to figure out this problem.
|
If you have 100 messages in a queue setting a trigger to fire when the first one shows up is futile - the first message showed up 99 messages ago and you missed it.
Please read the documentation on triggering. And think about what you're doing. Not necessarially in that order.
|
I need the documentation, give me some trail. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 04, 2008 1:07 am Post subject: Re: trigger is not working |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zlj wrote: |
| I need the documentation, give me some trail. |
Link at the top of this page.
"Starting applications using triggering"
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jlc |
| Posted: Thu Dec 04, 2008 3:32 am Post subject: |
|
|
Novice
Joined: 27 Nov 2008
Posts: 10
|
Question, if you run the application that you triggering manually, do you see the messages getting processed (do they disapear from the queue)? Here I'm trying to make sure that your application is running fine before moving forward troubleshooting any MQ stuff.  |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Dec 04, 2008 6:27 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jlc wrote: |
| Question, if you run the application that you triggering manually, do you see the messages getting processed (do they disapear from the queue)?... |
Yes...provided the manual start provides the queue manager name and queue name for the application - I'm assuming you have followed best practice here and coded the application to be started either by triggering, or by command line.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 04, 2008 7:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I need the documentation, give me some trail. |
WMQ Application Programming Guide and WMQ Application Programming Reference.
I'd suggest trigtype(first). With trigtype(depth), the qmgr turns triggering off for this queue (as documented in the above manuals) once the trigger fires. Trigtype(depth) requires that the application (or sysadmin) to turn triggering back on.
It would help if you would copy/paste your definitions here.
1) tirggered qlocal definition
2) Process definition
3) initiation queue definition
and
4) your c: or $ prompt interaction when you start the trigger monitor.
5) your c: or $ prompt interaction when you put message(s) to the queue
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
