Академический Документы
Профессиональный Документы
Культура Документы
ON WEBSPHERE MQ
Document Overview
This knowledge document discusses case study of various Dead letter queue Scenario's Note: All scenario's are tested on WMQ version 7.0.1.0 & on Window's platform. Version 1 Creation Date 05/15/12 Nature of Change Initial Draft
Setup: Sender: Qmname: QM1 , Remote Queue: QM2.QR, Xmitq: QM2 Channel: QM1.QM2 Receiver: Qmname: QM2, Local Queue: LQ1, Process: P1 Channel: QM1.QM2
INDEX
S.No 1 2 3 4 5 6 7 8 9 10 Table of Contents Destination queue does not exist. Message put(attribute) have been inhibited on the destination queue. Destination queue is full. Message is too large. Messages put to an alias queue go to DEAD.LETTER.QUEUE with reason MQRC_UNKNOWN_ALIAS_BASE_Q. Msg directly kept in xmit queue. MSG IS TOO BIG FOR CHL FOR BOTH SDR/RCVR. If the TRIGGER MONITOR fails to start the application, it places the Trigger message in the DLQ Miscellaneous Contact US Page No 4 4 5 6 7 8 9 10 11 12
On QM2:
One message went to LQ1 and rest of the 3 messages went to Deadq.
Scenario 5: Messages put to an alias queue go to DEAD.LETTER.QUEUE with reason MQRC_UNKNOWN_ALIAS_BASE_Q. On QM1 Rname is pointing to LQ.A which is an alias queue on QM2.
Put 3 messages on QM2.QR on QM1, which went to queue alias LQ.A ,but target queue doesn't exits, so message finally will reside in deadq.
All messages has been stuck at xmitq QM2, because sender channel is stopped.
Note: MQFB Feedback Values: http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic= %2Fcom.ibm.mq.csqzaq.doc%2Ffc_MQFB_.htm&resultof=%22mqfb%22 MQFB_XMIT_Q_MSG_ERROR Feedback indicating that a message channel agent has found that a message on the transmission queue is not in the correct format. The message channel agent puts the message on the dead-letter queue using this feedback code. 8
Scenario 7: MSG IS TOO BIG FOR CHL FOR BOTH SDR/RCVR. A) MAXMSGL is 5 for Sender channel, so that big message can stuck at channel.
Put 3 big messages on QM2.QR remote queue on QM1. All message will go to QM1 deadq.
B) MAXMSGL is 5 for Receiver channel, so that big message will stuck at channel and went to deadq. ON qm1:
On QM2:
Scenario: 8: If the TRIGGER MONITOR fails to start the application, it places the Trigger message in the DLQ
We have deleted Test.txt file from target location. 3 messages has been put.
Now all (3) messages has been delivered to dead letter queue on Target host. 10
Miscellaneous: Other Scenario's which are not possible to test on stand alone system: 1. Sender is not authorized to use the destination queue. 2. A user exit has requested this action The reason code is that supplied by the user exit, or the default MQRC_SUPPRESSED_BY_EXIT (This reason code occurs only on z/OS.) Infor Center link: http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic= %2Fcom.ibm.mq.csqzaq.doc%2Ffc_MQFB_.htm&resultof=%22mqfb%22 3. Issue with Dynamic queue (Dynamic queue is deleted)
11
Contact Us:
Vineeth S: vineets1@in.ibm.com Vikrant Singh Malik: vikrmali@in.ibm.com
12