| Author |
Message
|
| gavze007 |
 Posted: Wed Apr 11, 2018 3:14 am Post subject: Dead letter queue location 0? |
 |
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
Hi,
I'm having a weird issue in one of our connections. Everything seems okay but no messages are being transferred (on both directions).
We'ere using MQ 9 and the client uses MQ 7.
It's a regular connection - remote queues with a sender channel and local queues with a receiver channel.
When we try to put a test message on the remote queue (local at the client), the sender channel starts but the client doesn't receive anything.
When the client tries to put a test message on our queues (remote on his side), the receiver channel starts but no message passes.
An event is written:
During the processing of channel 'TO.NJ3U.CAS.1' 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 0, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.
Where is DLQ in location 0? Is there something I'm missing when checking this issue?
Thanks in advance |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Apr 11, 2018 4:13 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
How do you know no messages are being transferred, have you checked the channel status to determine that's the case?
Does the channel remain in a running state when this happens, or does it go into retry?
What is the NPMSPEED setting of the channels?
Are the messages persistent?
Are the channels at each end authorised to use the DLQ?
Are there any messages on the Dead-Letter Queue (DLQ) in either queue manager?
Have you queried your queue manager for the name of its specified DLQ, which will give you its 'location'?
My questions may seem endless, but these are all things that should be checked and used to fault-diagnose before posting...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gavze007 |
| Posted: Wed Apr 11, 2018 11:23 pm Post subject: |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
| exerk wrote: |
How do you know no messages are being transferred, have you checked the channel status to determine that's the case?
Does the channel remain in a running state when this happens, or does it go into retry?
What is the NPMSPEED setting of the channels?
Are the messages persistent?
Are the channels at each end authorised to use the DLQ?
Are there any messages on the Dead-Letter Queue (DLQ) in either queue manager?
Have you queried your queue manager for the name of its specified DLQ, which will give you its 'location'?
My questions may seem endless, but these are all things that should be checked and used to fault-diagnose before posting... |
I don't see any messages on my local queues when the client sends me, and it's the same on the other direction.
The channel is always on running state, even when stopping and starting it there is no error and the channel starts successfully on both directions.
The NPMSPEED setting of all channels is set to fast
The local queues are all defined as persistent.
How can I know if the channels are authorized to use the DLQ?
There are no messages on any DLQ, as the location we get is 0 that is neither of them.
I checked the QMGR on my side and I know what is my QMGR, but still the event logged points me to location 0.
Thanks |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 11, 2018 11:47 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gavze007 wrote: |
| I don't see any messages on my local queues when the client sends me, and it's the same on the other direction. |
What are you using to put test messages?
| gavze007 wrote: |
| The channel is always on running state, even when stopping and starting it there is no error and the channel starts successfully on both directions. |
And you have checked the status to see whether the channel has actually NOT sent anything down the pipe?
| gavze007 wrote: |
| The NPMSPEED setting of all channels is set to fast |
I suggest you read the Knowledge Centre (KC) in regard to the implications of that.
| gavze007 wrote: |
| The local queues are all defined as persistent. |
As has been stated on this site, many times before, queues are NOT, repeat NOT, persistent or non-persistent - messages are! If your application is deciding on that setting, it will over-ride what is set for the queue. Again, read the KC in regard to the attribute PERSISTENT(YES | NO) of a queue, because there is a correlation between NPMSPEED(FAST) channels, whether a DLQ has been specified or not, whether a channel has the authority to put to a DLQ, and message persistence.
| gavze007 wrote: |
| How can I know if the channels are authorized to use the DLQ? |
Look in the KC, because that's more effective than me just giving you the answer!
| gavze007 wrote: |
| There are no messages on any DLQ, as the location we get is 0 that is neither of them. |
The zero is irrelevant - I assume that the DLQs in each queue manager have been identified and checked, including for any automatic DLQ-Handler actions?
| gavze007 wrote: |
| I checked the QMGR on my side and I know what is my QMGR, but still the event logged points me to location 0. |
Again, the zero is irrelevant so don't fixate on it. Query the queue manager properties for the name of the queue, and check it!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Thu Apr 12, 2018 2:15 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
This sounds like a bug to me. I'd be tempted to raise a PMR and ask PMR why their message makes no sense
In the meantime it might be worth running the channel with MQ trace on. You should be able to fairly easily see the message coming across the channel (if it does) and see what happens to it.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Last edited by PaulClarke on Thu Apr 12, 2018 10:09 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 12, 2018 4:05 am Post subject: Re: Dead letter queue location 0? |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| gavze007 wrote: |
An event is written:
During the processing of channel 'TO.NJ3U.CAS.1' 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 0, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue. |
Where is this event written?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 12, 2018 4:28 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I thought it was just me. Same issue here. How are you supposed to make any sense of these error messages?
While the error message is useless, at least we can look at the Dead Letter Header of the message in the DLQ to see what queue is involved.
| Quote: |
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'.
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'.
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'. |
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| gavze007 |
| Posted: Thu Apr 12, 2018 4:32 am Post subject: Re: Dead letter queue location 0? |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
| bruce2359 wrote: |
| gavze007 wrote: |
An event is written:
During the processing of channel 'TO.NJ3U.CAS.1' 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 0, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue. |
Where is this event written? |
On my server when the client sends me a message |
|
| Back to top |
|
|
| gavze007 |
| Posted: Thu Apr 12, 2018 4:49 am Post subject: |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
| PeterPotkay wrote: |
I thought it was just me. Same issue here. How are you supposed to make any sense of these error messages?
While the error message is useless, at least we can look at the Dead Letter Header of the message in the DLQ to see what queue is involved.
| Quote: |
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'.
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'.
----- amqrmrca.c : 1574 -------------------------------------------------------
03/30/2018 05:44:31 AM - Process(124848.12588) User(mqm) Program(amqrmppa)
Host(ctomqcnhd961) Installation(Installation1)
VRMF(8.0.0.6) QMgr(MyQmgrNameHere)
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'TO.MyQmgrNameHere.ClusterNameHere' 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 1, 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 '124848'. |
|
In your case you have a normal location for the DLQ - 1.
On the event's I'm getting it says the location is 0 which is non of the DLQs. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 12, 2018 4:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gavze007 wrote: |
| On the event's I'm getting it says the location is 0 which is non of the DLQs. |
What is the value returned for 'DIS QMGR DEADQ', for your queue manager?
What is the value returned for 'DIS CHL(<your RCVR name>) USEDLQ', for your queue manager?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gavze007 |
| Posted: Thu Apr 12, 2018 5:16 am Post subject: |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
QMGR:
DIS QMGR DEADQ
1 : DIS QMGR DEADQ
AMQ8408: Display Queue Manager details.
QMNAME(****) DEADQ(DEAD.LETTER.QUEUE)
Channels:
DIS CHL(****) USEDLQ
3 : DIS CHL(****) USEDLQ
AMQ8414: Display Channel details.
CHANNEL(****) CHLTYPE(SDR)
USEDLQ(YES)
DIS CHL(****) USEDLQ
4 : DIS CHL(****) USEDLQ
AMQ8414: Display Channel details.
CHANNEL(****) CHLTYPE(RCVR)
USEDLQ(YES) |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 12, 2018 5:23 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And that queue is empty, with no automated DLQ Handler running against it?
What is your sending party setting the messages to, persistent, or non-persistent?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gavze007 |
| Posted: Thu Apr 12, 2018 5:43 am Post subject: |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
Yes the DLQ is empty
The client is sending persistent messages |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Apr 12, 2018 6:02 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| gavze007 wrote: |
| Yes the DLQ is empty |
So they're not going there then...
| gavze007 wrote: |
| The client is sending persistent messages |
Or not, as is the case 
Ask the client to:
1. STOP their SDR;
2. PUT some test messages to you;
3. Check that the messages appear on their XMITQ to you;
4. End the application they're using to put the test messages, and see if they 'disappear' when the application ends, or remain on the XMITQ;
5. START their SDR and see if the XMITQ queue depth drops to zero;
6. Wait a reasonable amount of time and STOP their SDR again;
7. See if the messages roll back on to the XMITQ, or are successfully transferred to you.
You could do the same for your end.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gavze007 |
| Posted: Thu Apr 12, 2018 6:44 am Post subject: Re: Dead letter queue location 0? |
|
|
Novice
Joined: 28 Mar 2018
Posts: 19
|
| bruce2359 wrote: |
| bruce2359 wrote: |
| gavze007 wrote: |
An event is written:
During the processing of channel 'TO.NJ3U.CAS.1' 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 0, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue. |
Where is this event written? |
I meant precisely and exactly where in the file-system path did you see the error. |
Windows application log |
|
| Back to top |
|
|
|
|
