| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| runmqdlq --not putting messages on the FWDQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mensch |
 Posted: Tue May 30, 2006 11:33 pm Post subject: runmqdlq --not putting messages on the FWDQ |
 |
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi
We are running MQ5.3 CSD10 on solaris 5.9.
I was trying to put messages from DLQ to the FWD queue by running following command
runmqdlq < DLQ.CFG > DLQ.LOG
DLQ.CFG contains
INPUTQ(DLQ) INPUTQM(QMGR)
REASON (*) ACTION(FWD) FWDQ(INQ) HEADER(NO)
When I run this, I am getting following error
AMQ8722: Dead-letter queue handler unable to put message: Rule 2 Reason 2334
Went through MQMessages.pdf , But couldent get proper answer.
Please Help.
NB: QMGR is default Queue manager
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed May 31, 2006 2:29 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
2334 (X'091E')
MQRC_RFH_ERROR
Explanation:
An MQPUT or MQPUT1 call was issued, but the message data contains an MQRFH or MQRFH2 structure that is not valid. Possible errors include the following:
* The StrucId field is not MQRFH_STRUC_ID.
* The Version field is not MQRFH_VERSION_1 (MQRFH), or MQRFH_VERSION_2 (MQRFH2).
* The StrucLength field specifies a value that is too small to include the structure plus the variable-length data at the end of the structure.
* The CodedCharSetId field is zero, or a negative value that is not valid.
* The BufferLength parameter of the call has a value that is too small to accommodate the structure (the structure extends beyond the end of the message).
Completion Code:
MQCC_FAILED
Programmer Response:
Check that the fields in the structure are set correctly. Ensure that the application sets the CodedCharSetId field to a valid value (note: MQCCSI_DEFAULT, MQCCSI_EMBEDDED, MQCCSI_Q_MGR, and MQCCSI_UNDEFINED are not valid in this field). |
Do you know which process is placing this message on the DLQ? Does it work if you try HEADER(YES)?
Can you use amqsbcg to dump the mqmd and the first 100 bytes of the problem message for us?
_________________
-wayne |
|
| Back to top |
|
|
| Mensch |
| Posted: Wed May 31, 2006 5:56 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi
Thanks for your prompt reply.
Messages are going to FWD Queue with Header set to Yes.... But I wonder how those messages wil get processed as Mesages in FWD Queue now contain Dead letter header as well .
Anyways thanks again!!
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed May 31, 2006 6:07 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
It looks like the message in the DLQ has a corrupted RFH(2) header. Again, it would be useful to see the mqmd and top portion of that message.
What do you want to do with this message after it goes to the FWD queue? You would need some process to repair the rfh2.
_________________
-wayne |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
