| Author |
Message
|
| karthik_ps |
 Posted: Sun Dec 04, 2011 1:14 am Post subject: MQRC_TRUNCATED_MSG_ACCEPTED Error |
 |
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Dear All,
I want to create a trigger to clear the message once its arrived in a particular queue. Hence, i created a trigger and assigned to that queue. I have given a trigtype as "every". I wrote a small shell script in unix env which calls java function to clear the message. When I am running that shell script manually, its working fine. It is clearing all message present in the queue. But when I am trying the same using trigger, I am getting below exception.
runmqtrm -m A.B.BRK.QMGR -q A.B.BRK.QMGR.AB.INQ
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079
When I searched in mqrc, i found the meaning as "MQRC_TRUNCATED_MSG_ACCEPTED". Could someone help me how to resolve this. Thanks in advance. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Dec 04, 2011 5:29 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| karthik_ps wrote: |
| Hence, i created a trigger and assigned to that queue. |
What queue is 'that queue'?
Please post the queue definitions for 'that queue'.
Please post the PROCESS object definitions 'that queue' identifies.
Post one of the trigger messages in the initiation 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 |
|
|
| karthik_ps |
| Posted: Sun Dec 04, 2011 6:05 am Post subject: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Dear Jedi,
Thanks for the reply.
Please find below details.
dis q(TST.GRL.BRK.QMGR.SBR.INQ)
1 : dis q(TST.GRL.BRK.QMGR.SBR.INQ)
AMQ8409: Display Queue details.
QUEUE(TST.GRL.BRK.QMGR.SBR.INQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2011-12-03)
ALTTIME(11.43.29) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2009-10-24) CRTIME(14.07.37)
CURDEPTH(24) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE)
IPPROCS(0) MAXDEPTH(5000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) TRIGGER
NPMCLASS(NORMAL) OPPROCS(1)
PROCESS(PROC1) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(EVERY) USAGE(NORMAL)
--------------------------------------------------------------------
dis process(PROC1)
3 : dis process(PROC1)
AMQ8407: Display Process details.
PROCESS(PROC1) APPLTYPE(UNIX)
APPLICID(/EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH)
ENVRDATA( ) USERDATA( )
DESCR( ) ALTDATE(2011-12-04)
ALTTIME(11.39.34)
--------------------------------------------------------------------
dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
4 : dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.INITIATION.QUEUE)
TYPE(QLOCAL) ACCTQ(QMGR)
ALTDATE(2008-11-19) ALTTIME(10.29.2
BOQNAME( ) BOTHRESH(0)
CLUSNL( ) CLUSTER( )
CLWLPRTY(0) CLWLRANK(0)
CLWLUSEQ(QMGR) CRDATE(2008-11-19)
CRTIME(10.29.2 CURDEPTH(0)
DEFBIND(OPEN) DEFPRTY(0)
DEFPSIST(NO) DEFSOPT(SHARED)
DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Initiation Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ( )
IPPROCS(0) MAXDEPTH(1000)
MAXMSGL(1000) MONQ(QMGR)
MSGDLVSQ(PRIORITY) NOTRIGGER
NPMCLASS(NORMAL) OPPROCS(0)
PROCESS( ) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(NONE) USAGE(NORMAL)
---------------------------------------------------------------------
Kindly let me know why i have to post trigger msg in initiation queue. I already posted msg in TST.GRL.BRK.QMGR.SBR.INQ queue and tested.
Thanks for your kind support.
Regards,
Karthikeyan |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 04, 2011 6:53 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Two queues are involved in triggering.
1) the application queue - your business messages are put/get
2) the initiation queue - trigger event messages
When a message arrives in the application queue (correctly configured for triggering), the qmgr creates a trigger event message from information you define in the application queue definition, AND from the process object definition. The qmgr puts the trigger message to the initiation queue.
The trigger monitor (runmqtrm) waits for a trigger event message to arrive, gets a trigger message, then starts the consuming application that you named in the process object.
The consuming app gets the business message from the application queue.
I want to see if a trigger event message was successfully put to the initq by the qmgr. If not, the consuming app will not start.
Instead of 'post', perhaps I should have asked you to display (with any handy utility) a trigger event message from the initq.
_________________
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 |
|
|
| bruce2359 |
| Posted: Sun Dec 04, 2011 7:49 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| karthik_ps wrote: |
dis q(TST.GRL.BRK.QMGR.SBR.INQ)
1 : dis q(TST.GRL.BRK.QMGR.SBR.INQ)
AMQ8409: Display Queue details.
QUEUE(TST.GRL.BRK.QMGR.SBR.INQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2011-12-03)
ALTTIME(11.43.29) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2009-10-24) CRTIME(14.07.37)
CURDEPTH(24) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE)
IPPROCS(0) MAXDEPTH(5000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) TRIGGER
NPMCLASS(NORMAL) OPPROCS(1)
PROCESS(PROC1) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(EVERY) USAGE(NORMAL)
--------------------------------------------------------------------
dis process(PROC1)
3 : dis process(PROC1)
AMQ8407: Display Process details.
PROCESS(PROC1) APPLTYPE(UNIX)
APPLICID(/EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH)
ENVRDATA( ) USERDATA( )
DESCR( ) ALTDATE(2011-12-04)
ALTTIME(11.39.34)
--------------------------------------------------------------------
dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
4 : dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.INITIATION.QUEUE)
TYPE(QLOCAL) ACCTQ(QMGR)
ALTDATE(2008-11-19) ALTTIME(10.29.2
BOQNAME( ) BOTHRESH(0)
CLUSNL( ) CLUSTER( )
CLWLPRTY(0) CLWLRANK(0)
CLWLUSEQ(QMGR) CRDATE(2008-11-19)
CRTIME(10.29.2 CURDEPTH(0)
DEFBIND(OPEN) DEFPRTY(0)
DEFPSIST(NO) DEFSOPT(SHARED)
DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Initiation Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ( )
IPPROCS(0) MAXDEPTH(1000)
MAXMSGL(1000) MONQ(QMGR)
MSGDLVSQ(PRIORITY) NOTRIGGER
NPMCLASS(NORMAL) OPPROCS(0)
PROCESS( ) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(NONE) USAGE(NORMAL) |
Note what I marked in bold. There are no trigger event messages in the initiation queue. The trigger didn't fire.
Your display of the TST.GRL.BRK.QMGR.SBR.INQ application queue did NOT include the TRIGGER attribute value. Did you omit it deliberately? What is the TRIGGER attribute for this queue?
Try this command: DISPLAY QL(TST.GRL.BRK.QMGR.SBR.INQ) TRIGGER
_________________
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 |
|
|
| PeterPotkay |
| Posted: Sun Dec 04, 2011 9:09 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| bruce2359 wrote: |
| karthik_ps wrote: |
dis q(TST.GRL.BRK.QMGR.SBR.INQ)
1 : dis q(TST.GRL.BRK.QMGR.SBR.INQ)
AMQ8409: Display Queue details.
QUEUE(TST.GRL.BRK.QMGR.SBR.INQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2011-12-03)
ALTTIME(11.43.29) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2009-10-24) CRTIME(14.07.37)
CURDEPTH(24) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ(SYSTEM.DEFAULT.INITIATION.QUEUE)
IPPROCS(0) MAXDEPTH(5000)
MAXMSGL(4194304) MONQ(QMGR)
MSGDLVSQ(PRIORITY) TRIGGER
NPMCLASS(NORMAL) OPPROCS(1)
PROCESS(PROC1) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(EVERY) USAGE(NORMAL)
--------------------------------------------------------------------
dis process(PROC1)
3 : dis process(PROC1)
AMQ8407: Display Process details.
PROCESS(PROC1) APPLTYPE(UNIX)
APPLICID(/EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH)
ENVRDATA( ) USERDATA( )
DESCR( ) ALTDATE(2011-12-04)
ALTTIME(11.39.34)
--------------------------------------------------------------------
dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
4 : dis q(SYSTEM.DEFAULT.INITIATION.QUEUE)
AMQ8409: Display Queue details.
QUEUE(SYSTEM.DEFAULT.INITIATION.QUEUE)
TYPE(QLOCAL) ACCTQ(QMGR)
ALTDATE(2008-11-19) ALTTIME(10.29.2
BOQNAME( ) BOTHRESH(0)
CLUSNL( ) CLUSTER( )
CLWLPRTY(0) CLWLRANK(0)
CLWLUSEQ(QMGR) CRDATE(2008-11-19)
CRTIME(10.29.2 CURDEPTH(0)
DEFBIND(OPEN) DEFPRTY(0)
DEFPSIST(NO) DEFSOPT(SHARED)
DEFTYPE(PREDEFINED)
DESCR(WebSphere MQ Default Initiation Queue)
DISTL(NO) GET(ENABLED)
HARDENBO INITQ( )
IPPROCS(0) MAXDEPTH(1000)
MAXMSGL(1000) MONQ(QMGR)
MSGDLVSQ(PRIORITY) NOTRIGGER
NPMCLASS(NORMAL) OPPROCS(0)
PROCESS( ) PUT(ENABLED)
QDEPTHHI(80) QDEPTHLO(20)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QDPMAXEV(ENABLED) QSVCIEV(NONE)
QSVCINT(999999999) RETINTVL(999999999)
SCOPE(QMGR) SHARE
STATQ(QMGR) TRIGDATA( )
TRIGDPTH(1) TRIGMPRI(0)
TRIGTYPE(NONE) USAGE(NORMAL) |
Note what I marked in bold. There are no trigger event messages in the initiation queue. The trigger didn't fire.
|
If the Init Queue is not open for Input (see in red above), presumably by a trigger monitor, the QM will not waste its time creating a trigger message. Trigger Condition #8.
Karthik_ps, create a new local queue to be used as an Init queue for this app. Don't use the SYSTEM.DEFAULT.INITIATION.QUEUE, its not best practice to use this queue. Before you test again, verify your trigger monitor has your new Init queue open, make sure your app queue is modified to reference your Init queue instead of the SYSTEM.DEFAULT.INITIATION.QUEUE.
Also, you probably don't need or want Trigger Type Every. 9 out of 10 times Trigger On First with an app that loops on the queue until its empty is the better way.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Dec 04, 2011 9:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Regarding TRIGTYPE(EVERY)... there has been quite a bit of discussion here regarding its use, misuse, and (potential) problems arising from both. 
_________________
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 |
|
|
| exerk |
| Posted: Sun Dec 04, 2011 9:35 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bruce2359 wrote: |
| ...Your display of the TST.GRL.BRK.QMGR.SBR.INQ application queue did NOT include the TRIGGER attribute value. Did you omit it deliberately? What is the TRIGGER attribute for this queue? |
The attribute is TRIGGER, and it's there in the display posted...
_________________
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: Sun Dec 04, 2011 9:51 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Ah! I stand corrected. I was applying the alphabetic search technique. Who would have thought TRIGGER would be in the M's, and not with the T's - along with the other trigger attributes?
_________________
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 |
|
|
| bruce2359 |
| Posted: Sun Dec 04, 2011 10:52 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| karthik_ps wrote: |
runmqtrm -m A.B.BRK.QMGR -q A.B.BRK.QMGR.AB.INQ
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079
When I searched in mqrc, i found the meaning as "MQRC_TRUNCATED_MSG_ACCEPTED". Could someone help me how to resolve this. Thanks in advance. |
The -q switch on runmqtrm needs to specify the initiation queue you named in the initiation queue attribute of the application queue.
In your configuration, -q SYSTEM.DEFAULT.INITIATION.QUEUE.
The truncated message came from the A.B.BRK.QMGR.AB.INQ queue - which is not the initiation queue you specified.
_________________
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 |
|
|
| mqjeff |
| Posted: Mon Dec 05, 2011 1:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| bruce2359 wrote: |
| Ah! I stand corrected. I was applying the alphabetic search technique. Who would have thought TRIGGER would be in the M's, and not with the T's - along with the other trigger attributes? |
It's with the N's, for "NOTRIGGER". (Presumably) |
|
| Back to top |
|
|
| karthik_ps |
| Posted: Mon Dec 05, 2011 5:53 am Post subject: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Dear Peter & Jedi,
Thanks for your detailed explanation. I understood the concept.
As you advised, i have created a exclusive INITIATION QUEUE and its working fine.
Now the trigger event is calling the shell script and clearing the messages from the queue.
But my query is why everytime its throwing 2079 warning message. What can we do to avoid it ?
Please see the screen output
************************************************************
svositst% runmqstrm -m TST.GRL.BRK.QMGR -q TST.GRL.BRK.QMGR.SBR.INQ
zsh: command not found: runmqstrm
svositst% runmqtrm -m TST.GRL.BRK.QMGR -q TST.GRL.BRK.QMGR.SBR.INQ
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
Trigger message with warning 2079
************************************************************
Please find command below.
-----------------------------------------------------------------------------
dis process(PROC1)
AMQ8407: Display Process details.
PROCESS(PROC1) APPLTYPE(UNIX)
APPLICID(/EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH)
ENVRDATA( ) USERDATA( )
DESCR( ) ALTDATE(2011-12-04)
ALTTIME(11.39.34)
DIS Q(INITIATION.QUEUE)
AMQ8409: Display Queue details.
QUEUE(INITIATION.QUEUE) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2011-12-05)
ALTTIME(16.30.56) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2011-12-05) CRTIME(16.30.56)
CURDEPTH(0) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR(initiation queue description) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ( ) IPPROCS(0)
MAXDEPTH(5000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
NOTRIGGER NPMCLASS(NORMAL)
OPPROCS(0) PROCESS( )
PUT(ENABLED) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA( ) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(NORMAL)
DISPLAY QL(TST.GRL.BRK.QMGR.SBR.INQ)
9 : DISPLAY QL(TST.GRL.BRK.QMGR.SBR.INQ)
AMQ8409: Display Queue details.
QUEUE(TST.GRL.BRK.QMGR.SBR.INQ) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2011-12-05)
ALTTIME(16.32.55) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2009-10-24) CRTIME(14.07.37)
CURDEPTH(23) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(ENABLED) HARDENBO
INITQ(INITIATION.QUEUE) IPPROCS(0)
MAXDEPTH(5000) MAXMSGL(4194304)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
TRIGGER NPMCLASS(NORMAL)
OPPROCS(1) PROCESS(PROC1)
PUT(ENABLED) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA( ) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(FIRST)
USAGE(NORMAL)
------------------------------------------------------------------------------ |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Dec 05, 2011 6:13 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
The -q switch needs to identify the initiation queue, and not an application queue. Try this command:
runmqtrm -m TST.GRL.BRK.QMGR -q INITIATION.QUEUE
The warning about truncated message is occurring because runmqtrm is getting your application messages from your application queue (the -q switch); and runmqtrm's message buffer is only big enough for a trigger event message - not one of your application messages.
_________________
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 |
|
|
| karthik_ps |
| Posted: Mon Dec 05, 2011 7:20 am Post subject: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Dear Jedi,
Please find output for the command.
svositst% runmqtrm -m TST.GRL.BRK.QMGR -q INITIATION.QUEUE
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
WebSphere MQ trigger monitor started.
__________________________________________________
Waiting for a trigger message
/EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH 'TMC 2TST.GRL.BRK.QMGR.SBR.INQ PROC1 /EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH TST.GRL.BRK.QMGR '
sh: /EXPORT/IBM/HOME/MBID/KARTHI/SBRCLEARQ.SH: not found
Error starting triggered application.
__________________________________________________
Now the message is not clearing from the queue and its holding there.
Regards,
Karthik |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 05, 2011 7:31 am Post subject: Re: MQRC_TRUNCATED_MSG_ACCEPTED Error |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| karthik_ps wrote: |
| Now the message is not clearing from the queue and its holding there. |
Because now the trigger is firing correctly but the script being triggered (sbrclearq.sh) can't be found in the path being used.
There are a number of posts in this forum regarding the environment a triggered process uses you might find helpful.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
