| Author |
Message
|
| tanishka |
 Posted: Tue Feb 02, 2010 9:21 am Post subject: message goes to dead letter queue |
 |
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
Hi,
I try to put message on local queue and messages goes to dead letter queue. can any one let me know what could be the reason. below is content of dead letter queue.
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 573 bytes
00000000: 444C 4820 0100 0000 0000 0100 574D 422E 'DLH ........W.'
00000010: 5749 4353 2E41 4942 414C 5245 504C 5920 'W.REPLY '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 5742 524B ' WBRK'
00000040: 3631 5F44 4546 4155 4C54 5F51 5545 5545 '61_DEFAULT_QUEUE'
00000050: 5F4D 414E 4147 4552 2020 2020 2020 2020 '_MANAGER '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: B501 0000 2020 2020 2020 2020 0B00 0000 '╡... ....'
00000080: 5765 6253 7068 6572 654D 5149 6E74 6567 'WebSphereMQInteg'
00000090: 7261 746F 7236 2020 2020 2020 3230 3130 'rator6 2010'
000000A0: 3032 3032 3137 3039 3530 3030 3030 3739 '0202170950000079' |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 02, 2010 9:38 am Post subject: Re: message goes to dead letter queue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tanishka wrote: |
| I try to put message on local queue and messages goes to dead letter queue. can any one let me know what could be the reason. |
What version of WMQ? Put to the local queue how? Using what software (and how does this connect to the content of the message)? What OS?
What have you already done to try and resolve this problem?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tanishka |
| Posted: Tue Feb 02, 2010 10:19 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| V 6.0, Using RFHUTIL, AMQSBCG, on Windows |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 02, 2010 10:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| tanishka wrote: |
| Using RFHUTIL, |
Then why does the DLH show a different application as being responsible for putting the message? Is there something about your configuration that might be helpful if you shared it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tanishka |
| Posted: Tue Feb 02, 2010 10:33 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| Nothing to share. I created queue and trying to put message using rfhutil and i am getting this problem. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 02, 2010 10:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Taniska -
The name of the queue manager appears to be that created by the Broker 6.1 Default Configuration Wizard. The application that appears to be PUTTING this message, at least according to the contents of the DLH you have provided is "WebSphereMQIntegator6"
Are you sure you don't want to amend your statement to say you are using RFHUTIL to send a REQUEST message to a broker flow, that is then putting a message on the DLQ? |
|
| Back to top |
|
|
| tanishka |
| Posted: Tue Feb 02, 2010 10:50 am Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 02, 2010 11:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Then why didn't you mention this in your original post? 
So your actual question becomes "why does the broker put my message to the dead letter queue", to which the short answer is "because there's something wrong with the way you've set it up" and the slightly longer (and more useful) answer is "because it's encountering an error and you'll find the details in the broker log".
Which, if you were putting a request message into broker and not getting the expected result, is the first place you should have looked. Followed in short order by a user trace to obtain additional information!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 02, 2010 11:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to more relevent section in light of new & pertinent information
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tanishka |
| Posted: Tue Feb 02, 2010 12:36 pm Post subject: |
|
|
Centurion
Joined: 24 Nov 2008
Posts: 144
|
| Thanks for replys. and will work on it |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Tue Feb 16, 2010 3:42 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| tanishka wrote: |
| Thanks for replys. and will work on it |
Good !!
YOu can run the Trace commands, as soon as you put the message on the queue and broker picks it up for the processing. Apply the trace nodes(before and/or after the compute node, if you are using that) and observe the trace log closely. YOu would certainly get the cause of the problem.
Best of luck !
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
