| Author |
Message
|
| ms_mq |
 Posted: Fri Dec 28, 2007 4:47 am Post subject: MQ trigger issue |
 |
|
Acolyte
Joined: 23 Feb 2007
Posts: 69
|
Hi,
I have a triggered queue running on an AIX queue manager. The messages are coming to the queue and it has to trigger an application, but that is not happening.The trigger monitor for that initiation queue is running.
The only recent change is the AIX server was rebooted and since then we are having this issue. Could you please advise what could be the problem? Currently, we are running the application manually to clear the messages.
Please help.
_________________
Regards,
MS |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Dec 28, 2007 7:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Show us the triggered queue's attributes...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ms_mq |
| Posted: Fri Dec 28, 2007 7:27 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007
Posts: 69
|
Please find the queue details:
AMQ8409: Display Queue details.
QUEUE(APP.DATA.ACTQMGR) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2007-12-2
ALTTIME(02.47.32) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2005-10-02) CRTIME(07.44.3
CURDEPTH(0) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR(Inbound message) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ(APP.INITQ) IPPROCS(2)
MAXDEPTH(10000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
TRIGGER NPMCLASS(NORMAL)
OPPROCS(1) PROCESS(DATA.TRAN)
PUT(ENABLED) QDEPTHHI(10)
QDEPTHLO(5) QDPHIEV(ENABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA( ) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(NORMAL)
_________________
Regards,
MS |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Dec 28, 2007 7:34 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
OPPROCS(1) , I can see a process attached to here.
and the CURDEPTH(0).
Did you put some messages and verified the same
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Dec 28, 2007 8:30 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
OPROCS doesn't have any effect on triggering.
IPROCS is 2 though. Why should MQ trigger the app if it sees something already has the q open for MQGETs? In other words, you are not meeting all the Trigger Conditions spelled out in Chapter 13 of the APG, so no trigger as designed.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Dec 28, 2007 8:34 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hey
Sorry, I misplaced, really sorry, its IPROCS(2).
Regards
gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 28, 2007 12:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| PeterPotkay wrote: |
OPROCS doesn't have any effect on triggering.
IPROCS is 2 though. Why should MQ trigger the app if it sees something already has the q open for MQGETs? In other words, you are not meeting all the Trigger Conditions spelled out in Chapter 13 of the APG, so no trigger as designed. |
Just to be complete, once you have resolved IPPROCS situation,
you do have a trigger monitor running on APP.INITQ right? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
