| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message with ¬¬¬ going into DLQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sonal |
 Posted: Wed Dec 22, 2010 10:30 am Post subject: Message with ¬¬¬ going into DLQ |
 |
|
Apprentice
Joined: 20 Mar 2009
Posts: 45
|
Hi Experts,
Im trying to put a message in my REQ queue:
1.0ABCDXM00000 270 T002456 EFG0000###~9~12052010105555~9001~ SG~7001360144~1012051055551~10735.00~82735.00~82735.00~90611.95~12~10735.00~~N~0~~~~L~~¬¬¬~###\
The mesg is half FR (The first 100 bytes) and the rest is tilde delimited.
The problem is, when the '¬¬¬' is included in message (see the 2nd last field of the mesg), the message is going in the DLQ of broker queue manager. However, if I replace this '¬¬¬' with any other value like '%%%', it doesnt go into DLQ and works well.
The hex code for '¬¬¬' is ACAC AC.
Do you've any idea why is it happening ? I suppose irrespecive of what we are sending in mesg, it shouldnt go into DLQ of broker. Or, is there some kind of symbols (Hex code) for which the mesgs goes into DLQ ?
In the properties of REQ queue in my message flow, I did the following trials with the Advance option of REQ queue properties:
Convert : checked
Convert encoding : 0
Convert coded character set Id: 819
Convert : checked
Convert encoding : 0
Convert coded character set Id: 0
Convert : unchecked
Convert encoding : disabled
Convert coded character set Id: disabled
Pls help me.
Many thanks... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Dec 22, 2010 10:39 am Post subject: Re: Message with ¬¬¬ going into DLQ |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sonal wrote: |
| Do you've any idea why is it happening ? I suppose irrespecive of what we are sending in mesg, it shouldnt go into DLQ of broker. Or, is there some kind of symbols (Hex code) for which the mesgs goes into DLQ ? |
Well, if you tried something like looking at dead letter header on the message, rather than just going, "ooo a message in the DLQ" you'd know why it had been dead lettered.
Yes, there's a magic sequence of hex bytes which makes broker dead letter a message. There's another one that makes broker delete your hard drive. 
Alternatively, you could discover that the message has been dead lettered with a reason code not in the 2000-3000 range, indicating an application error. Given that the application in this case is broker, you might then think to take a user trace and see what's abending.
Or you could just cut to the chase, run a user trace anyway and see why broker's dead lettering the message. It's possible you'll see something like this:
| Code: |
| BIP0666E Specific sequence of hex bytes detected in message. Message will be dead lettered |
I doubt it. But I've been proved wrong on this forum once this week already, and Christmas is a time for miracles.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
