You can see effective heartbeat in the management UI on the connection page.
Heartbeats do not close connection and it't not correct that connection should be considered dead in 1.5 seconds with a 3 second interval: it will be 3 seconds. I'm curious if Langohr simply tries to re-connect because missed heartbeats are treated the same way as connection loss in recent Java client versions: is connection recovery enabled? > On 14 abr 2016, at 14:20, David Smith <shmish...@gmail.com> wrote: > > Can anyone help me with this > http://stackoverflow.com/questions/36596446/rabbitmq-langohr-no-heartbeat > > I am setting up a connection to Rabbit using > > (rmq/connect (assoc (:rabbit conf) :requested-heartbeat 3)) > I have 3 subscribers to 3 channels, no producers. When I shutdown the rabbit > server, nothing happens to my client. I would expect it to report missing > heartbeat after 1.5 seconds and close the connection after 3 seconds. I have > left the program running with rabbit down for quite a few minutes and nothing. > > I'm using langohr 3.5.1 > > I have checked .getHeartbeat rabbit-conn and it is correctly set to 3. I have > also tried setting :connection-timeout 5 which I believe is 5ms. If I set > that to 1 then my app fails to start up (timeout too small to make the > initial connection), so I'm sure that setting is correct as well. > > -- > You received this message because you are subscribed to the Google Groups > "clojure-rabbitmq" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure-rabbitmq+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
