[rabbitmq-discuss] Noticed way too many open connections

cw storm cwstorm at gmail.com
Mon Dec 2 21:10:37 GMT 2013

Thanks Michael.  So if I set heartbeat timeout, if the specific
conn/channel hasn't been closed for a specified time, then the rabbit
server will close that connection/channel, right?  Is there any harm in
putting this in the code?  I want to make sure that this is good practice
and such.


On Mon, Dec 2, 2013 at 2:20 PM, Michael Klishin <michael.s.klishin at gmail.com
> wrote:

> 2013/12/2 cw storm <cwstorm at gmail.com>
>>  I'm thinking of adding setConnectionTimeOut to the open connection
>> service so that if that connection/channel did not close properly, the
>> rabbit mq server will close it after the timeout has been reach.  Please
>> let me know if this is best practice or not.
> setConnectionTimeOut configures a value that's passed to Socket#connect.
> What you want to set is heartbeat timeout
> (say, to 30-60 seconds). Note that both server and client do not
> immediately detect when their peer is unreachable
> due to how TCP works (TCP connections will sit there in TIME_WAIT state
> for some time). Heartbeats
> enable such situations to be detected earlier.
> --
> MK
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131202/2c697574/attachment.html>

More information about the rabbitmq-discuss mailing list