| Author |
Message
|
| Heidils |
 Posted: Wed Sep 10, 2003 2:11 am Post subject: Dead Letter Header Reason 65536 |
 |
|
Novice
Joined: 25 May 2003
Posts: 11
Location: SA
|
Hi
I have a client that is sending us messages to a local queue on our mq server. On this queue a WMQI flow is running that should pick up and process all these messages. This flow has been done in such a way that any exceptions or errors will go directly to a deadletter queue set up to catch all these errors.
However of the say 100 messages that I receive 94 gets processed immediatly and 6 of these messages lands on the SYSTEM.DEAD.LETTER.QUEUE. This happens randomly and if I reprocess these message from the system dead letter queue they go through without a problem.
It seems as if they don't even get picked up by this processed but thrown right out on the SYSTEM.DEAD.LETTER.QUEUE.
The DLH reason code is 65536. Where can I start looking for the cause of this problem?
Thanks!
Heidi-Lize
 |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Wed Sep 10, 2003 6:18 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
How did you READ the DLQ message and how did you interpret the reason code?
Cheers
Kumar |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Sep 10, 2003 7:07 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
That code is the fist 'User Defined' one for DLH. It's also the one that MQSI uses when it puts messages on the DLQ.
Take a look at the MQSI logs/NT Event log (you didn't say what platform) to determine why MQSI kicked the messages out.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Heidils |
| Posted: Thu Sep 11, 2003 4:30 am Post subject: |
|
|
Novice
Joined: 25 May 2003
Posts: 11
Location: SA
|
Hi Guys
Thanks for the replies
Kumar, I read the deadletter queue header by looking at the message properties of the message on the SDLQ and the Dead Letter Header Tab. This is where I got the 65536 code.
I tried the runmqdlq command - this threw all the message back on to the input queue and they were processed with no problem.
The command I used: runmqdlq SYSTEM.DEAD.LETTER.QUEUE QMGRNAME
wait(no)
action(retry)
ctrl Z
ctrl Z
Eddie , we are running MQ Series 5.3 CSD 3(?) on a windows NT environment with MQSI 2.1 CSD 4
I looked at the event log (application and event) but could not see any error msg's for that time.
My queue properties for both the input and output queues on this flow has been set to Max queue depth of 5000 and max msg length of 4194304. The msg received's length was 2043 and they've only send us 100 msg's at a time.
Any other ideas?
Thanks!
 |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Sep 11, 2003 6:32 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
The 65536 code shows that an application put the message on the DLQ. You could also look at the MQ logs, but I don't think you'll find anything, because MQ didn't put the message there.
If MQSI put it there, then I'm surprised that there is nothing logged. Can't think of anywhere to look at, at the moment.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
