| Author |
Message
|
| paragupt |
 Posted: Wed Sep 01, 2010 6:17 am Post subject: MQ triggering shows a weird behaviour on first trigger |
 |
|
Newbie
Joined: 13 Jun 2007
Posts: 9
|
Hello All,
I have installed WebSphere MQ 7.0.1.2 and done the triggering in it as shown below:
DEFINE QLOCAL ('A.TRANS') +
DESCR('INITIATION QUEUE FOR TRIGGER + ON A.TRANS') +
USAGE(NORMAL) +
REPLACE
DEFINE QLOCAL ('QL.A.TRANS') +
DESCR('Accuterm Warehouse TRANS transactions received on this queue') +
DEFPSIST(YES) +
MAXDEPTH(100000) +
MAXMSGL(1048754) +
MSGDLVSQ(FIFO) +
USAGE(NORMAL) +
TRIGGER +
TRIGTYPE(FIRST) +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGDATA(' ') +
PROCESS('PR.A.TRANS') +
INITQ('A.TRANS') +
REPLACE
DEFINE PROCESS ('PR.A.TRANS') +
DESCR('App program') +
APPLTYPE(WINDOWS) +
APPLICID('D:\Program Files\MQToSQL.exe') +
REPLACE
DEFINE SERVICE ('SRVC.A.TRANS') +
DESCR('TRIGGER + SERVICE A.TRANS') +
STARTCMD('runmqtrm') +
STARTARG('-m QM.A -q A.TRANS') +
STOPCMD('amqsstop') +
STOPARG('-m QM.A -p +MQ_SERVER_PID+') +
CONTROL(QMGR) +
SERVTYPE(SERVER) +
REPLACE
I have posted around 1000 messages in local queue and trigger monitor started the application. after say 300 messages are processed, my application stopped(as designed) but now trigger monitor started the application again as soon as it is stopped(although there is no trigger message in the initq). I am unable to stop my app if trigger monitor/service is running. I even tried to kill my application but it started again. AS per infocentre, I have checked the trigger interval of Queue manager also and it is in default of 999,999,999.
Please let me know if this is working as per designed or there is a bug in MQ. I am unable to find any documentation which validates this.
Thanks a Lot!!! |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Sep 01, 2010 6:25 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Working as designed.
When a trigger on first q is closed and all other trigger conditions are true and there are move that 0 messages on the queue, a new trigger message is generated. This is documented in the manuals.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| paragupt |
| Posted: Wed Sep 01, 2010 6:36 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2007
Posts: 9
|
| Thanks a lot Peter for a quick reply. Can you please give me a link(I am unable to find it in the info center. I have looked it 3 times but every times I think I have skipped it.) of the page where it is documented. This will help me a lot in presenting it to the management. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 01, 2010 6:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| paragupt wrote: |
| Can you please give me a link(I am unable to find it in the info center. I have looked it 3 times but every times I think I have skipped it.) of the page where it is documented. |
Try here or the surrounding area.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 01, 2010 6:57 am Post subject: Re: MQ triggering shows a weird behaviour on first trigger |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| paragupt wrote: |
| I have posted around 1000 messages in local queue and trigger monitor started the application. after say 300 messages are processed, my application stopped(as designed) |
Why is it designed like this (I ask as it's not a best practice pattern & there may be another way to achieve your ends).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
