[rabbitmq-discuss] Messages unexpectedly moving from Unacked to Ready
pat at munkiisoft.com
Fri Jan 31 11:44:54 GMT 2014
Looks like it was the load balancer (LB), as you suggested, because when we
configured the code to go direct at a specific node in the cluster rather
than via the LB it works as expected.
Wrt the AMQP heartbeat. We are using the official >NET client and I am now
setting the RequestedHeartbeat property, on the factory, to 10 (seconds).
Is that how I control that heartbeat? It was defaulting 0.
On 30 January 2014 17:28, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 30/01/14 17:26, Patrick Long wrote:
>> 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
>> <http://10.206.20.1:2750> -> 10.206.20.167:5672
> 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?
> That's down to how the load balancer is configured. If the load balancer
> is closing connections because it perceives them to be inactive, lowering
> the AMQP heartbeat interval might prevent you from having to reconfigure
> the load balancer.
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, Pivotal
Patrick Long - Munkiisoft Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss