| Author |
Message
|
| Mensch |
 Posted: Fri May 05, 2006 6:22 am Post subject: Qmgr putting messages in DLQ |
 |
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi all
I m runing MQ5.3 on solaris servers (Say A and B) . B is sending messages to A using Channels. At B I have MB5.2 with rules and formatter which routes messages to different legacy systems connected to B through ftp.
for some cases , once A is sending messages to B , QMGR at B is putting those messages in DLQ at B .
I m not able to find out why it is doing so?
Could you please tell me probable reasons why QMGR puts messages to DLQ?
I checked connectevity between B and Legacy systems . but it is fine.
Please help
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
 |
| jlamond |
| Posted: Fri May 05, 2006 6:40 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
You should look at the dead letter queue reason code... Mosst of the time it is a destination error (queue not found) or security issue (not authorized).
_________________
Jean-Marc |
|
| Back to top |
|
|
| Mensch |
| Posted: Fri May 05, 2006 6:48 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi
Thank you very much for your reply ..
Destination is not a queue , Actually at B connector is running which converts messages in to files and FPTs to the external system so i think Destination q not found is noty a reason
also about security , till today all messages were going properly to the external system .
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
|
| jlamond |
| Posted: Fri May 05, 2006 7:05 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
In which queue manager do you find the message in the dead letter Queue ?
If you deal with a connector, it is most probably related to the fact that the connector cannot process the message correctly and respect the default action define in the report option DEAD_LETTER_QUEUE (report option 0, which is the default). This is quiet commun from connector. This is the way to avoir 'poison message' that would hang any other message to be process, since the 'poison message' is at the head of the queue.
_________________
Jean-Marc |
|
| Back to top |
|
|
| Mensch |
| Posted: Fri May 05, 2006 7:11 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2005
Posts: 166
|
Hi
the Queue manager at B is putting messages in DLQ.
I am not able to fine reason in the DLH .
this is what I am getting in the DLH
CorrelId=' ',Length=-1,Data='DLH IN_QUEUE QMGR_B 3MQHRF WebSphereMQIntegrator5 2006050308440100RFH P MQSTR OPT_APP_GRP NNSAP OPT_MSG_TYPE ...Data
Please let me know IF you could find the reason
_________________
Thanks and Regards ,
Mensch |
|
| Back to top |
|
|
| sirsi |
| Posted: Fri May 05, 2006 7:29 am Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
| search in the forum... u will know how to find the reason code in DLH |
|
| Back to top |
|
|
| jlamond |
| Posted: Fri May 05, 2006 8:35 am Post subject: |
|
|
Voyager
Joined: 28 May 2002
Posts: 94
Location: Paris
|
ok, so it is as I expect to connector (WMQMB) that put the message in the dead letter queue. The reason code appear in binary right after the DLH header. The easiest way to look at is to use the amgsbcg program that is supply with MQ. On unix, /opt/mqm/samp/bin On Microsoft tools\C\bin..
The source code is also provide (for syntax).
Regards
_________________
Jean-Marc |
|
| Back to top |
|
|
|
|
