[rabbitmq-discuss] Often failed to produce message due to TIMEOUT WAITING FOR ACK
Wong Kam Hoong
wongkamhoong at gmail.com
Wed Sep 26 07:18:16 BST 2012
What's the general health of your rabbit when this happens?
The RabbitMQ nodes seems fine during the incident happened:
*Master Node Usage*
Memory : 300M
CPU % : Average 30%
*Slave Node Usage*
Memory : 130M
CPU % : Average 30%
Plenty of free memory and disk?
Yes, there are plenty of free memory and disk space in both servers.
Are you using mirrored/HA queues at all?
Yes, I'm using HA in all queues.
Could there possibly be a spike, i.e. lots of messages getting published in
a short space of time?
No, I checked there are only few messages during that time, e.g. 2012-09-26
03:28:32 => 4 messages
No strange errors in the logs?
After the incident happened RabbitMQ did logged warning, e.g.
=WARNING REPORT==== 26-Sep-2012::03:29:25 ===
closing AMQP connection <0.8661.18> (192.168.0.100:46151 ->
=INFO REPORT==== 26-Sep-2012::03:29:37 ===
accepting AMQP connection <0.8897.18> (192.168.0.100:43836 ->
On Tue, Sep 25, 2012 at 2:32 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:
> On 25/09/12 03:46, Wong Kam Hoong wrote:
>> com.rabbitmq.client.**ShutdownSignalException: clean channel shutdown;
>> reason: #method<channel.close>(reply-**code=406, reply-text=TIMEOUT
>> WAITING FOR ACK, class-id=0, method-id=0)
>> Based on the log, the problem seems like related to "*NACKS Received*"
>> and "*ChannelN*" code throw the TimeoutException with reply-code *406
> I don't think it has anything to do with nacks - unless you are actually
> seeing some exception mentioning nacks.
> Looks like a straightforward timeout.
> I check all RabbitMQ servers are still working fine and I believe the
>> time I set for *waitForConfirmsOrDie *(10000) should be sufficient enough.
> 10s should indeed generally be long enough. But one can certainly envision
> scenarios where it won't be. What's the general health of your rabbit when
> this happens? Plenty of free memory and disk? No strange errors in the
> logs? Are you using mirrored/HA queues at all? Could there possibly be a
> spike, i.e. lots of messages getting published in a short space of time?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss