Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

I am traveling till mid-May, we will see how it goes. > On 22 abr 2016, at 13:35, David Smith wrote: > > Hi Guys, > > I realise you are busy, I'm just checking the status on this to make sure it > doesn't get forgotten :) > > When I posted the issue initially it was just

Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

Hi Guys, I realise you are busy, I'm just checking the status on this to make sure it doesn't get forgotten :) When I posted the issue initially it was just a theoretical problem but we have now had a situation where it caused real problems. Thanks, David. On Thursday, April 14, 2016 at

Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

Attached is a wireshark capture, hope this helps. -- 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

Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

No, I wasn't referring to the TCP connection timeout. Can you please take a Wireshark capture? Our team is quite busy this and next week. > On 14 abr 2016, at 17:42, David Smith wrote: > > What I see in langohr is that the following are set: > > (doto cf >

Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

OK, that also reveals that RabbitMQ is running in a remote host, which I expected but wasn't sure. Are there any load balancers involved? > On 14 abr 2016, at 17:33, David Smith wrote: > > Nothing in the logs, just the open connection line then nothing: > > =INFO

Re: [clojure-rabbitmq] RabbitMQ Langohr no heartbeat

I have tried (connection (assoc (:rabbit conf) :requested-heartbeat 3 :automatically-recover false :connection-timeout 5)) based on what you said but no joy, I would have thought I would at least see something in the logs to suggest it's trying to do something. I thought the connection was