[rabbitmq-discuss] Unexpected server crash and .NET API: disconnect is not detected?
Emile Joubert
emile at rabbitmq.com
Thu Mar 31 13:26:10 BST 2011
Hi Alfonso,
On 31/03/11 12:52, Alfonso Pantoja wrote:
> Listing connections ...
> guest 192.168.0.121 62966 running
>
> (checked after more than 5 minutes after killing the application)
> Using TCPVIEW (SysInternals tools) there is no connection from my
> machine to the server.
It sounds like the broker thinks there is a connection but the client
has already left. AMQP contains a heartbeat feature that will detect
this situation and tear down the connection if the client doesn't
respond. You can turn heartbeats on using
ConnectionFactory.RequestedHeartbeat.
Regards
Emile
More information about the rabbitmq-discuss
mailing list