| Author |
Message
|
| prk |
 Posted: Fri Jul 16, 2004 5:53 pm Post subject: Weird problem - Msg ending up in DLQ instead of local queue |
 |
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
When a message is sent from AIX to Windows the msg ends up in the DLQ even though the local queue name matches exacly as the one specified in the remote definition.
When tested with a diff queue name on both the sides it works fine. Deleted the queue and recreated the queue on both the ends but we have the same problem.
_________________
Thank You,
Varma |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jul 16, 2004 6:01 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Messages that end up in the Dead Letter Queue have a Dead Letter Header in them.
That Dead Letter Header contains a Reason Code.
That Reason Code tells you why the message ended up on the Dead Letter Queue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jul 16, 2004 9:38 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is the message going to AIX DLQ or Windows DLQ?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| prk |
| Posted: Sun Jul 18, 2004 2:29 pm Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
The message is in the DLQ on Windows. Here is the message that was sent from AIX which went to the DLQ on windows.
00000000 DLH .... ....MQSI 444C4820 01000000 00000100 4D515349
00000016 .QL.ADV. OUT 2E514C2E 4144562E 4F555420 20202020
00000032 20202020 20202020 20202020 20202020
00000048 HHAR 20202020 20202020 20202020 48484152
00000064 DNQ01 444E5130 31202020 20202020 20202020
00000080 20202020 20202020 20202020 20202020
00000096 .... 20202020 20202020 20202020 11010000
00000112 3...MQST R .... 33030000 4D515354 52202020 0B000000
00000128 WebSpher eMQInteg 57656253 70686572 654D5149 6E746567
00000144 rator5 2004 7261746F 72352020 20202020 32303034
00000160 07182219 0600Hi t 30373138 32323139 30363030 48692074
00000176 here, I am comin 68657265 2C204920 616D2063 6F6D696E
00000192 g from t he Advan 67206672 6F6D2074 68652041 6476616E
00000208 tex 746578
Any help would be greatly appreciated.
_________________
Thank You,
Varma |
|
| Back to top |
|
|
| prk |
| Posted: Sun Jul 18, 2004 2:48 pm Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Here is the output for the DLQ message using amqsbcg on windows.
MQOPEN - 'SYSTEM.DEAD.LETTER.QUEUE'
MQGET of message number 1
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 437
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D512044455641445630312020202040F7FFBF20001A01'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'DEVADV01 '
** Identity Context
UserIdentifier : 'mqm '
AccountingToken :
X'0332313600000000000000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : ' '
PutDate : '20040718' PutTime : '22192689'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 211 bytes
00000000: 444C 4820 0100 0000 0000 0100 4D51 5349 'DLH ........MQSI'
00000010: 2E51 4C2E 4144 562E 4F55 5420 2020 2020 '.QL.ADV.OUT '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 4848 4152 ' HHAR'
00000040: 444E 5130 3120 2020 2020 2020 2020 2020 'DNQ01 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 1101 0000 ' ....'
00000070: 3303 0000 4D51 5354 5220 2020 0B00 0000 '3...MQSTR ....'
00000080: 5765 6253 7068 6572 654D 5149 6E74 6567 'WebSphereMQInteg'
00000090: 7261 746F 7235 2020 2020 2020 3230 3034 'rator5 2004'
000000A0: 3037 3138 3232 3139 3036 3030 4869 2074 '071822190600Hi t'
000000B0: 6865 7265 2C20 4920 616D 2063 6F6D 696E 'here, I am comin'
000000C0: 6720 6672 6F6D 2074 6865 2041 6476 616E 'g from the Advan'
000000D0: 7465 78 'tex '
No more messages
MQCLOSE
MQDISC
C:\Program Files\IBM\WebSphere MQ\bin>
The put and the Get are enabled on the queue. I also deleted the queue and recreated the queue with a script shown below.
DEFINE QL(MQSI.QL.ADV.OUT) +
DESCR('ADVANTEX TO ORCOM') +
DEFPSIST(YES) +
PUT(ENABLED) +
GET(ENABLED) +
NOTRIGGER +
USAGE(NORMAL) +
REPLACE
This is completely weird and I would really appreciate any help.
_________________
Thank You,
Varma |
|
| Back to top |
|
|
| kirani |
| Posted: Sun Jul 18, 2004 2:52 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
It's hard to interpret the Dead Letter Header like this. Use MQSeries Explorer to browse the Dead Letter queue. Look for Reason Code in Dead Letter header tab.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| TonyD |
| Posted: Sun Jul 18, 2004 3:00 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| I think you will find that the DLH Code x'00000100' (really x'00 01 00 00' as it is little-endian) resolves to reason code '65536' which is MQSI's way of saying that a message flow had an error but had no backout or failure queue to route the message to. Possibly there is a queue name mismatch somewhere in the flow? |
|
| Back to top |
|
|
| prk |
| Posted: Mon Jul 19, 2004 5:15 pm Post subject: |
|
|
Centurion
Joined: 17 Feb 2004
Posts: 102
|
Hi Guys,
Thanks a lot for all your support. The problem has was that there was a error handling flow which was running and was expecting an XML message on the local queue and when a regular msg is put to that queue it was getting backed out to the DLQ by the flow.
Thanks once again for the quick responses. |
|
| Back to top |
|
|
|
|
