| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| another noob question |
« View previous topic :: View next topic » |
| Author |
Message
|
| cscheer |
 Posted: Tue Aug 15, 2006 12:04 pm Post subject: another noob question |
 |
|
Novice
Joined: 15 Aug 2006
Posts: 13
|
I am working with another company at a remote site as the receiving queue. I have created a setup, just like I did in my test env, and here it does not work. In test I have two boxes, one a sdr on a rcvr. There it works fine. With the real company, we are just a sdr. The error I keep getting is
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'BOAFNI.QMV1.TO.TS2V' one or more messages
could not be put to the destination queue and attempts were made to put them to
a dead-letter queue. The location of the queue is 2, where 1 is the local
dead-letter queue and 2 is the remote dead-letter queue.
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '3835'.
But I have my network folks sniffing the line and they do not even see a packet come out of the system. So, it can't be them, it has to be me. I am at a loss. I keep digging through the MANY books for MQ, but don't get anywhere. The info above states it put more info to the remote dead-letter queue. But if no packets even leave my system, how can it put it on the remote system.
We are really taking a beating for this, but we as a whole, have never used MQ before. |
|
| Back to top |
|
 |
| mvic |
| Posted: Tue Aug 15, 2006 12:47 pm Post subject: Re: another noob question |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| cscheer wrote: |
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '3835'. |
1. carry out the actions listed above. Look at both local and remote dead letter queues. If you don't have one defined, then define one. Reading messages (specifically, their dead letter headers) from the DLQ is somewhat complicated - but when you have understood what is going on, it should be OK.
2. Although you're assured no packets were received at the remote end, nonetheless it's just good sense to request they look at their dead letter queue, because that's where this MQ message implies it attempted to put your message.
What versions of MQ, the OS, etc. are you running? |
|
| Back to top |
|
|
| cscheer |
| Posted: Tue Aug 15, 2006 1:20 pm Post subject: |
|
|
Novice
Joined: 15 Aug 2006
Posts: 13
|
MQ 5.3, HPUX 11.11
Not sure how to define a remote dead letter or assign it. |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Aug 15, 2006 1:33 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 15, 2006 1:37 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You won't be able to create the dead letter queue on the remote queue manager - unless the partner has decided to give you MQM ownerships.
You can ask them if they have anything on their dead letter queue , and if they say "what?" then ask them to define one.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
