Author |
Message
|
srinivasraom |
Posted: Wed Oct 18, 2006 4:24 am Post subject: Trigger Event is not generating on Queue |
|
|
Apprentice
Joined: 18 May 2006 Posts: 31
|
Hi,
I hava a local queue, which is associated with a init queue and a process queue. When a message comes in the local queue, trigger event is not generating. My local queue attributes are given below. Can anyone guess what could be the problem.
DIS QL(SG_MSGTR_IN_QUEUE)
14 : DIS QL(SG_MSGTR_IN_QUEUE)
AMQ8409: Display Queue details.
DESCR(Application queue for Message Translator - ti2bo)
PROCESS(SG_MSGTR_IN_PROCESS) BOQNAME( )
INITQ(SG_MSGTR_IN_INIT_QUEUE) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(SG_MSGTR_IN_QUEUE) CRDATE(2006-10-02)
CRTIME(11.03.16) ALTDATE(2006-10-1
ALTTIME(18.34.27) GET(ENABLED)
PUT(ENABLED) DEFPRTY(5)
DEFPSIST(YES) MAXDEPTH(640000)
MAXMSGL(104857600) BOTHRESH(999)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(FIFO)
RETINTVL(999999999) USAGE(NORMAL)
TRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(10) QDEPTHLO(1)
QDPMAXEV(ENABLED) QDPHIEV(ENABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(0)
OPPROCS(0) CURDEPTH(0)
Regards
Srini |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 4:30 am Post subject: Re: Trigger Event is not generating on Queue |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srinivasraom wrote: |
. Can anyone guess what could be the problem.
|
One of the conditions for triggering hasn't been met?
I'd check that the trigger monitor is running properly first. Try running it in foreground during testing so you can see the output. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
srinivasraom |
Posted: Wed Oct 18, 2006 5:20 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006 Posts: 31
|
We are running in foreground only. If see the process of triggering, if a message comes to queue, a trigger event should fire by the queue manager, which will take the trigger message and put into the init queue.
Trigger monitor will always look into the init queue. My question is trigger event is not generating, if i put message into the queue, it was there in the queue only. it was not coming to init queue. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 5:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srinivasraom wrote: |
We are running in foreground only. If see the process of triggering, if a message comes to queue, a trigger event should fire by the queue manager, which will take the trigger message and put into the init queue.
|
I stand by my previous assertion - one of the conditions for triggering is not being met. You need to work through the checklist; trigger monitor was just my first guess.
srinivasraom wrote: |
if i put message into the queue, it was there in the queue only. it was not coming to init queue. |
Just to clarify, for the record & the benefit of future readers, the message does not move to the init queue. The message stays in the destination and a separate trigger message is generated which goes to the init queue. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
srinivasraom |
Posted: Wed Oct 18, 2006 5:43 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006 Posts: 31
|
what could be the possible check list for this probelm ? |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 5:46 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
srinivasraom wrote: |
what could be the possible check list for this probelm ? |
I meant the list of conditions that need to be met for a trigger event to be generated - it's an obvious thing to say but clearly if one of these is not met, the event doesn't get generated!
I'm suggesting that you check for each one in turn in your situation. Some are clearly being met; TRIGPRTY for instance is ok in the definition you posted. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 5:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Duh ... TRIGMPRI !!
Sorry - fingers far too far from my brain - impulses having to go all the way up my spine.....  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Oct 18, 2006 6:25 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
First, make sure you have a trigger monitor process reading the initq SG_MSGTR_IN_INIT_QUEUE, i.e.
Code: |
runmqtrm -m QMGR -q SG_MSGTR_IN_INIT_QUEUE |
_________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 6:27 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Nigelg wrote: |
First, make sure you have a trigger monitor process reading the initq SG_MSGTR_IN_INIT_QUEUE, i.e.
Code: |
runmqtrm -m QMGR -q SG_MSGTR_IN_INIT_QUEUE |
|
Vitor wrote: |
I'd check that the trigger monitor is running properly first. |
I think I've already suggested that.....  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Oct 18, 2006 7:27 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
Yes, I saw that.
I thought I would spell it out in words of one syllable - maybe the trigger monitor was started to read the default initq rather than the custom one. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
Vitor |
Posted: Wed Oct 18, 2006 7:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Ok; fair point...  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|