| Author |
Message
|
| james |
 Posted: Fri Nov 11, 2005 8:07 am Post subject: Dead letter Queue messages |
 |
|
Novice
Joined: 10 Jan 2003
Posts: 18
|
Hi,
I see some of the messages are going to the dead letter Queue with reason code 2052. The content of the message doesnt give the correct information.
Content of the message :
DLH AMSMQS.43720E0620247F55 MQAPRD01 MQADMIN amqpcsea 2005111018045945 $
ý
MQAPRD01 is the Queue manager name.
This Queue manager is running on AIX machine
Could anyone of you help me in this matter.
Thanks in advance.
JAMES  |
|
| Back to top |
|
 |
| javagate |
| Posted: Fri Nov 11, 2005 8:12 am Post subject: |
|
|
Disciple
Joined: 15 Nov 2004
Posts: 159
|
Does the target queue still exist ? Your application may have caused this to happen.
_________________
WebSphere Application Server 7.0 z/OS &
MQ 6.0. I work with WebSphere in the real world not in some IBM lab. |
|
| Back to top |
|
|
| james |
| Posted: Fri Nov 11, 2005 8:33 am Post subject: |
|
|
Novice
Joined: 10 Jan 2003
Posts: 18
|
Hi,
Here is the amsbcg
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 2
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D51204D514150524430312020202043743098200D426A'
CorrelId : X'414D51204D514150524430312020202043743098200D4D08'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'MQAPRD01 '
** Identity Context
UserIdentifier : 'mqm '
AccountingToken : X'0334363600000000000000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : ' '
PutDate : '20051111' PutTime : '13362432'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 208 bytes
00000000: 444C 4820 0000 0001 0000 0804 414D 534D 'DLH ........AMSM'
00000010: 5153 2E34 3337 3433 3039 3832 3030 4434 'QS.43743098200D4'
00000020: 4430 3520 2020 2020 2020 2020 2020 2020 'D05 '
00000030: 2020 2020 2020 2020 2020 2020 4D51 4150 ' MQAP'
00000040: 5244 3031 2020 2020 2020 2020 2020 2020 'RD01 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 0000 4D51 4144 4D49 4E20 0000 0006 '....MQADMIN ....'
00000080: 616D 7170 6373 6561 0000 0000 0000 0000 'amqpcsea........'
00000090: 0000 0000 0000 0000 0000 0000 3230 3035 '............2005'
000000A0: 3131 3131 3133 3336 3234 3332 0000 0002 '111113362432....'
000000B0: 0000 0024 0000 0001 0000 000D 0000 0008 '...$............'
000000C0: 0000 0001 0000 0002 0000 0804 0000 0000 '................' |
|
| Back to top |
|
|
| paulgroo |
| Posted: Wed Nov 16, 2005 1:06 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hi,
This looks like MQ created a temporary queue because the original one (that application is expecting) has been removed or renamed perhaps? Check the properties of the queue aswell and make sure all your 'puts' and 'gets' are set correctly... |
|
| Back to top |
|
|
| Dug |
| Posted: Wed Aug 16, 2006 2:33 am Post subject: |
|
|
Newbie
Joined: 14 Aug 2006
Posts: 4
|
Hello,
I seem to be have the same issue on a production server as listed in this topic. With messages appearing on the DLQ with the 2052 reason code.
Exactly the same as James is getting.
I was wondering is there anyway to find out what application is issuing the PCF commands that are causing this problem.
Any help would be great.
Regards,
Doug. |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Aug 16, 2006 2:43 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Give us a amqsbcg dump of the message to have a look at....
_________________
-wayne |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Aug 16, 2006 2:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the problem is indeed a temporary dynamic queue being deleted before the reply can be sent then it's most likely created by the putting application and deleted by that application ending (no PCF commands necessary, with all respect to other posters).
This may not be an error condition. Consider - online application creates temporary queue for reply, sends request with these details in the reply to fields. Application waits for reply but due to network issues doesn't get one without the necessary period of opperator wait time. Application issues "Sorry, your request cannot be handled at this time" to user and ends, deleting the temporary queue. Once the network clears itself the reply turns up, has no queue to go to and ends up on the dead letter with a 2052.
It's for this reason request/replies in this scenario should have an expiry set.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Wed Aug 16, 2006 2:56 am Post subject: WMQTool |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hi Doug,
Try downloading this tool. http://www.niratul.com
I use it all the time to view messages/troubleshoot problems in MQ. It has a good bit more detail than the MQExplorer tool.
AMSMQS.43720E0620247F55 - definitely looks like a dymanic queue name
This is what I found on the 2052 message:
An Hobj queue handle specified on a call refers to a dynamic queue that has been deleted since the queue was opened. On z/OS, this can also occur with the MQOPEN and MQPUT1 calls if a dynamic queue is being opened, but the queue is in a logically-deleted state. See MQCLOSE for more information about this.
Corrective action: Issue an MQCLOSE call to return the handle and associated resources to the system (the MQCLOSE call will succeed in this case). Check the design of the application that caused the error.
It looks like theres a problem with the message before it gets to the queue manager, or as above, the queue that you're trying to 'put' to doesnt exist (because it's either dymanic or has been deleted).
Let me know how you get on! |
|
| Back to top |
|
|
| Dug |
| Posted: Wed Aug 16, 2006 3:09 am Post subject: |
|
|
Newbie
Joined: 14 Aug 2006
Posts: 4
|
Thanks for the swift replys.
Here is a dump of one of the messages.
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 2
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 850
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D5120555347454E3031502020202064BD0E442221D85D'
CorrelId : X'414D5120555347454E3031502020202064BD0E442221D312'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'USGEN01P '
** Identity Context
UserIdentifier : 'MUSR_MQAdmin'
AccountingToken :
X'160105150000006005A0EC08C6CB9A6626D3AEF003000000000000000000000B'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'BM\WEBSPH~1\bin\AMQPCSEA.EXE'
PutDate : '20060815' PutTime : '15292503'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 208 bytes
00000000: 444C 4820 0100 0000 0408 0000 414D 512E 'DLH ........AMQ.'
00000010: 3434 3045 4244 3634 3131 4433 3231 3232 '440EBD6411D32122'
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 5553 4745 ' USGE'
00000040: 4E30 3150 2020 2020 2020 2020 2020 2020 'N01P '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: 0000 0000 4D51 4144 4D49 4E20 0B00 0000 '....MQADMIN ....'
00000080: 424D 5C57 4542 5350 487E 315C 6269 6E5C 'BM\WEBSPH~1\bin\'
00000090: 414D 5150 4353 4541 2E45 5845 3230 3036 'AMQPCSEA.EXE2006'
000000A0: 3038 3135 3135 3239 3235 3033 0200 0000 '081515292503....'
000000B0: 2400 0000 0100 0000 1100 0000 1400 0000 '$...............'
000000C0: 0100 0000 0200 0000 0408 0000 0000 0000 '................'
I will keep you posted. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Aug 16, 2006 9:06 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| Dug wrote: |
| 00000000: 444C 4820 0100 0000 0408 0000 414D 512E 'DLH ........AMQ.' |
The DLH reason code is x'0408' or in base10: 2052. (You can look it up!)
In the future, you might try using a message editing tool that clearly lists the DLH reason code. MQ Visual Edit does just that. For more information or to download a free 30-day trial go to:
http://www.capitalware.biz/mqve_overview.html
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Aug 17, 2006 12:26 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I completely agree with Vitor's answer.
What further explanation are you looking for?
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Dug |
| Posted: Thu Aug 17, 2006 2:12 am Post subject: |
|
|
Newbie
Joined: 14 Aug 2006
Posts: 4
|
Hi,
Thanks again for the feedback.
Roger I put the DLH reason code error in my first post above. I tend to use QPasa config Manger or just Websphere explorer to view the message and header content.
I will try the visual edit tool as well thanks.
Nigelg & Vitor
The explanation sounds spot on.
My issue is that I am dealing with a QMgr with several applications connecting from different teams. I was wondering if there is anyway to find out what application put the message.
Regards,
Douglas. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 17, 2006 2:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the MQMD.PutApplication field is no use then your best bet is to examine the data for clues. I notice your example is via the command server from the user MUSR_MQAdmin.
Don't forget you can use the dead letter handler to move these messages to another queue for investigation. My preference is not to leave stuff on the DLQ as it gets a bit contact admin should it fill up (and unwieldy if there's a sizeable problem).
Of course, you could use the same program to delete the messages where they've failed to find a temporary queue. Perhaps easier than setting expiry, which would probably involve a program change.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 17, 2006 3:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Dug wrote: |
Hi,
Thanks again for the feedback.
Roger I put the DLH reason code error in my first post above. I tend to use QPasa config Manger or just Websphere explorer to view the message and header content.
I will try the visual edit tool as well thanks.
Nigelg & Vitor
The explanation sounds spot on.
My issue is that I am dealing with a QMgr with several applications connecting from different teams. I was wondering if there is anyway to find out what application put the message.
Regards,
Douglas. |
Adding another tool will not change anything. You seem fine with the tools you have. (I use QPasa myself...). Having said that I noticed that you are not getting a 2085 object does not exist on the temporary dynamic queue.
This leads me to suspect that the application is trying to receive a persistent message on a temporary dynamic queue. This is a design error and should be fixed. To receive a reply to message that is persistent you need a queue that is persistent. QPasa should tell you if the message in the DLQ is persistent.
Your application should be complaining that they never receive an answer...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 17, 2006 4:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it in any way possible that SYSTEM.ADMIN.COMMAND.QUEUE got changed to defpsist(yest)?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
