| Author |
Message
|
| vinay_s_s |
 Posted: Fri Jan 23, 2009 1:20 am Post subject: Messages going to the Dead Letter queue |
 |
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
Hi Team,
I'm stuck in a problem.
The message is being sent from SOURCE qmgr to DEST qmgr. The message is put to a remote queue on SOURCE, which is pointing to a local queue on DEST qmgr.
The problem is, the messages from SOURCE is reaching the DEST qmgr's dead letter queue. Error log shows no information.
If I point the remote queue on SOURCE to any local queue of DEST, the message goes to the dead letter queue.
Any lights on this?
SOURCE qmgr : WebSphere MQ 5.3 QMGR, Windows 2000 Advanced Server.
DEST qmgr : WebSphere MQ 6.0 QMGR, Windows 2003 Enterprise Server
Thanks in advance,
Vinay |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Jan 23, 2009 1:35 am Post subject: Re: Messages going to the Dead Letter queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinay_s_s wrote: |
| The problem is, the messages from SOURCE is reaching the DEST qmgr's dead letter queue. Error log shows no information. |
That's because there's no error. The queue manager is behaving normally.
Check the dead letter header on the messages to see why they're going there, and resolve as appropriate.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jan 23, 2009 1:35 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
MQ adds a DLH (dead letter header ) to the message that is put to the dead letter queue, this DLH holds a reason code why the message has been put there..
use one of the mq samples (e.g. amqsbcg) or supportpac (MO71, ....) do browse the dead letter queue, find the reason code in the DLH, look it up in the messages and codes manual (or use mqrc) and you know why.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| vinay_s_s |
| Posted: Fri Jan 23, 2009 2:34 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
This is the output of AMQSBCG. Can you please help me out to find out the reason code? TIA
MQGET of message number 536
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 437
Format : 'MQDEAD '
Priority : 0 Persistence : 1
MsgId : X'414D51204E544144575431202020202012EF364920DD2306'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'NTADWT1 '
** Identity Context
UserIdentifier : 'vinay_s_s '
AccountingToken :
X'160105150000009374756BB6389E26EC4B196F262E0E0000000000000000000B'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'D:\apps\mqm\bin\amqsput.exe '
PutDate : '20090123' PutTime : '09233962'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 194 bytes
00000000: 444C 4820 0100 0000 2C08 0000 4E54 5044 'DLH ....,...NTPD'
00000010: 5247 3420 2020 2020 2020 2020 2020 2020 'RG4 '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 4457 542E ' DWT.'
00000040: 4E54 5044 5247 342E 5353 5550 4441 5445 'NTPDRG4.SSUPDATE'
00000050: 5F54 454D 5020 2020 2020 2020 2020 2020 '_TEMP '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: B501 0000 4D51 5354 5220 2020 0B00 0000 '╡...MQSTR ....'
00000080: 6562 5370 6865 7265 204D 515C 6269 6E5C 'ebSphere MQ\bin\'
00000090: 616D 7172 6D70 7061 2E65 7865 3230 3039 'amqrmppa.exe2009'
000000A0: 3031 3233 3039 3233 3430 3031 5445 5354 '012309234001TEST'
000000B0: 204D 4553 5341 4745 2033 202D 2056 494E ' MESSAGE 3 - VIN'
000000C0: 4159 'AY ' |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 2:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinay_s_s wrote: |
| This is the output of AMQSBCG. Can you please help me out to find out the reason code? |
Certainly. First look up the header structure here then count to that point in the data.
Or use MO71 or RFHUtil or MQExplorer, all of which can read the header for you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| masteringmq |
| Posted: Fri Jan 23, 2009 2:47 am Post subject: |
|
|
Master
Joined: 20 Oct 2008
Posts: 200
|
Does local queue on DEST qmgr exist?. Also is the local queue on DEST qmgr full?
Also examine the first line of the message text:
00000000: 444C 4820 0100 0000 2C08 0000 4E54 5044 'DLH ....,...NTPD'
This is the beginning of the dead letter header (DLH). You need to find the reason code. For example "0000 0827", it is in hex code and means 2087 = MQRC_UNKNOWN_REMOTE_Q_MGR. It is difficult but you can try from first line to x line 
Last edited by masteringmq on Fri Jan 23, 2009 3:24 am; edited 3 times in total |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 3:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| masteringmq wrote: |
| Does local queue on DEST qmgr exist?. |
The original posting says that the messages are going to DLQ no matter what the target queue. Also I feel sure the poster's probably checked that.
Hence the correct course of action remains to check the code. If it turns out to be a 2085, then the poster will know that, despite his belief the queue exists, the queue manager can't find it and thus can investigate why this is (spelling error, case error, etc).
If I had GBP10 for each case I'd been told a queue absolutely existed despite a 2085, only to find there were 2 letters transposed in either the local or remote queue definition, I could afford a really good holdiday someplace! 
(GBP5 for each case of missing letters would ensure an upgrade - ah, business class......  )
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vinay_s_s |
| Posted: Fri Jan 23, 2009 3:30 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
| The local queue exists on the DEST, and the curdepth is 0. |
|
| Back to top |
|
|
| vinay_s_s |
| Posted: Fri Jan 23, 2009 3:35 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
Vitor,
If you thing that there is an error in the application code, why does it happen if i post messages from ampsput on SOURCE qmgr?
Regards,
vinay |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jan 23, 2009 3:35 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
well, if you think that this is not the problem, the follow the advise to analyze the data you got by amqsbcg.... find the reason code and then check what it means.
stop guessing and find out why.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 3:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinay_s_s wrote: |
| If you thing that there is an error in the application code, why does it happen if i post messages from ampsput on SOURCE qmgr? |
At what point did I say, imply or even hint that this was a problem with application code? 
If you're not going to read the advice you're being given, never mind not follow it, then why waste time posting? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vinay_s_s |
| Posted: Fri Jan 23, 2009 3:54 am Post subject: |
|
|
Apprentice
Joined: 17 Nov 2008
Posts: 39
|
Sorry Vitor,
I never meant that you said that there is a problem with the code.
> Hence the correct course of action remains to check the code.
I understood this sentence in a wrong way.
Apologies.  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jan 23, 2009 3:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vinay_s_s wrote: |
Sorry Vitor,
I never meant that you said that there is a problem with the code.
> Hence the correct course of action remains to check the code.
I understood this sentence in a wrong way.
Apologies. |
Ah, no, I see, I need to put my hands up to that; my use of the word "code" here is ambiguous.
Also may have overreacted a little; it's a bad day on the day job!
Matching apologies. 
Check the reason code in the DLH & you'll see the problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 23, 2009 4:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| 00000000: 444C 4820 0100 0000 2C08 0000 4E54 5044 'DLH ....,...NTPD' |
Do we have 082c or 2092? MQRC_XMIT_Q_USAGE_ERROR
Where do you put the messages? Does your remote queue by any chance point to an XMITQ? Are you putting messages directly to the XMITQ?
Something in your setup appears to not be right.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Fri Jan 23, 2009 4:37 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
uhh, you gave him the fish, while we tried to learn him fishing
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
