ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Debugging assistance...

Post new topic  Reply to topic
 Debugging assistance... « View previous topic :: View next topic » 
Author Message
EB
PostPosted: Tue Oct 11, 2005 1:48 am    Post subject: Debugging assistance... Reply with quote

Acolyte

Joined: 19 Mar 2004
Posts: 70

Hi all
We have a cluster running and are getting the following warning in the AMQERR001 log.

-------------------------------------------------------------------------------
> 10/11/2005 10:46:12
> AMQ9544: Messages not put to destination queue.
>
> EXPLANATION:
> During the processing of channel 'TO.MRPW302' 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 '3980(4184)'.
> ----- amqrmrca.c : 1318 -------------------------------------------------------

'TO.MRPW302' beeing the cluster receiver to itself. The question is why do we get this?
Could it be that time to live is to low and the message dies during transport?
(DLQ is empty)

Any advice is greatly appreciated.

Regards
EB
Back to top
View user's profile Send private message
wschutz
PostPosted: Tue Oct 11, 2005 2:26 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Quote:
ACTION:
> Examine the contents of the dead-letter queue.
Did you do this?
EDIT:
Quote:
(DLQ is empty)

_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
hopsala
PostPosted: Tue Oct 11, 2005 7:06 am    Post subject: Re: Debugging assistance... Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

EB wrote:
Could it be that time to live is to low and the message dies during transport?

(By "time to live" I assume you mean MQMD.Expiry) No, expired messages do not expire during transport, expiry is only checked upon MQGET, not during channel comm protocol.
EB wrote:
(DLQ is empty)

You are probably using non-persistent messages with NPMSPEED(FAST), which means that problematic np-msgs are chucked.
Another possib is that you have a very high message retry on your RCVR and maybe a large BATCHSZ to boot - but I assume you've waited long enough to count this out.
EB wrote:
The question is why do we get this?

If my guess was correct (that you are using non-persistent msgs), then send a few persistent messages across, then you'll see them in the DLQ and the desired mqrc. (you should probably set batchsz to 1 and msg retry to 0 to speed up your tests)
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Tue Oct 11, 2005 6:05 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

The expiry could still be very small, messages could be persistent or not, they are being placed on the DLQ, and then blinking away when he finally gets around to browsing the DLQ.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mq_developer
PostPosted: Wed Oct 12, 2005 1:13 pm    Post subject: Reply with quote

Voyager

Joined: 18 Feb 2002
Posts: 82

Couple of things ..

First to ensure the fact that MQ was able to put to the DLQ ,

1) Verify that there are no error messages in the Mqseries logs in relation to DLQ put failures , also its worth while checking the /var/mqm/errors logs and its associated FDCS if any.
2) Next if MQ was successfull in putting to DLQ and you are not able to view because of "time to live" factor - it can be confirmed by looking into Queue Statistics ( there are lot of monitoring tools that comes with this inbuilt feature )

This should help you atleast get closer to the problem, further from the results if it was time to live factor you might want to try Report options.

Good luck ..
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Debugging assistance...
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.