[rabbitmq-discuss] Messages unexpectedly moving from Unacked to Ready

[Patrick Long]

The load balancer closing connections would look something like this in the
RMQ logs, yes?

=WARNING REPORT==== 30-Jan-2014::15:25:08 ===
closing AMQP connection <0.31743.12> (10.206.20.1:2750 -> 10.206.20.167:5672
):
connection_closed_abruptly

Those happen between 1 and 3 times a minute. Is this a common problem? We
obviously need load balancing to make use of clustering.

Is there a way of keeping the connection Alive?

Pat




On 30 January 2014 17:13, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 30/01/14 17:10, Patrick Long wrote:
>
>> The only way I could see it happen was if one of the other processing
>> threads looking at the _*same *_queue called close. However they do not
>> share channels and I assume that closing on a channel different to the
>> one that retrieved the message would not effect the Unacked state,
>> correct?
>>
>
> That's correct. Closing a channel releases all the unacked messages on
> that channel...
>
> On 30/01/14 17:12, Patrick Long wrote:
>
>> Ah so that makes it sound like the connection does not need to be
>> closed by the specific channel for that to happen
>>
>
> ...and closing a connection implicitly closes all the channels on that
> connection, releasing all their unacked messages.
>
> Cheers, Simon
>
> --
> Simon MacMullen
> RabbitMQ, Pivotal
>



-- 
Patrick Long - Munkiisoft Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140130/ed2d5742/attachment.html>