[rabbitmq-discuss] Unexpected server crash and .NET API: disconnect is not detected?
alfonso.pantoja at gmail.com
Thu Mar 31 23:26:19 BST 2011
If requiring heartbeats is not usual then something is wrong with our
development RabbitMQ server? As I said it seems not detect unexpected client
Server and client machine (machine from the consumer is launched) are on the
same IP range.
What may be the cause of not detecting clients unexpected disconnections?
(by the way, the server in fact are 2 clustered servers running under ubuntu
10 server and client machine is Windows Vista)
2011/3/31 Matthias Radestock <matthias at rabbitmq.com>
> Alfonso Pantoja wrote:
>> That's is interesting.
>> We won't have many consumer/publisher applications but there will be quite
>> frequent (intensive) incoming messages. Also in this scenario it is critical
>> to detect unexpected disconnections.
>> So I'd better add support for customize this value in order to gain fine
>> control on production.
> Requiring heartbeats is by no means normal. They are usually only necessary
> when something weird is going on in the network infrastructure or
> client/server machine setup. Unfortunately that is all too common.
> Btw, another downside to short heartbeats is that if a client machine gets
> heavily loaded then connections may get dropped due to missed heartbeats.
> So, as a general rule, configure the heartbeat interval to be as long as
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss