Just installing it now On Thu, Apr 14, 2016 at 4:12 PM, Michael Klishin <mklis...@pivotal.io> wrote:
> 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 <shmish...@gmail.com> wrote: > > What I see in langohr is that the following are set: > > (doto cf > (.setClientProperties client-properties) > (.setUsername username) > (.setPassword password) > (.setVirtualHost vhost) > (.setHost host) > (.setPort final-port) > (.setRequestedHeartbeat requested-heartbeat) > (.setConnectionTimeout connection-timeout) > (.setRequestedChannelMax requested-channel-max)) > > > I am setting connection-timeout and requested-heartbeat, isn't that what > you meant by setting a timeout? > > On Thu, Apr 14, 2016 at 3:39 PM, David Smith <shmish...@gmail.com> wrote: > >> I'm using 3.5.1 which is the latest version according to github and >> clojars. >> >> I am running rabbit as a docker container using docker-machine and >> image rabbitmq:3-management >> >> On Thu, Apr 14, 2016 at 3:33 PM, Michael Klishin <mklis...@pivotal.io> >> wrote: >> >>> Langohr is a wrapper around RabbitMQ Java client and in recent versions >>> relies on it to also perform connection recocovery. >>> Heartbeats were never implemented in Clojure. >>> >>> Your Langohr version is from 2014 or so. Have you considered trying the >>> most recent release (or does it still use 2014 in client properties? Also >>> possible) >>> >>> Anyhow, investigating this kind if issues would be the same with every >>> client library:) >>> >>> On 14 abr 2016, at 17:29, David Smith <shmish...@gmail.com> wrote: >>> >>> It was just that it sounded like you were answering the question from a >>> Java perspective but didn't know anything about the Clojure wrapper, but I >>> can see from the connections page that you wrote it :) I couldn't see >>> anything about the heartbeat on the connections page, just: >>> >>> product Langohr >>> copyright Copyright (C) 2011-2014 Michael S. Klishin, Alex Petrov >>> capabilities >>> exchange_exchange_bindings: true >>> connection.blocked: true >>> authentication_failure_close: true >>> basic.nack: true >>> publisher_confirms: true >>> consumer_cancel_notify: true >>> information See http://clojurerabbitmq.info/ >>> version 3.0.x >>> platform Clojure 1.8.0 on Java HotSpot(TM) 64-Bit Server VM 1.8.0_66 >>> >>> On Thu, Apr 14, 2016 at 3:25 PM, Michael Klishin <mklis...@pivotal.io> >>> wrote: >>> >>>> It is. What difference does it make? We need to base our assumptions on >>>> data and network traffic capture is the best data we can get. Server logs >>>> are also helpful and trivial to collect. >>>> >>>> On 14 abr 2016, at 17:22, David Smith <shmish...@gmail.com> wrote: >>>> >>>> Isn't this a mailing list for the Clojure client? >>>> >>>> On Thu, Apr 14, 2016 at 2:21 PM, Michael Klishin <mklis...@pivotal.io> >>>> wrote: >>>> >>>>> Also, please post full RabbitMQ logs and ideally a Wireshark traffic >>>>> capture. With the amount of information we have at the moment the best we >>>>> can do is guessing. >>>>> >>>>> On 14 abr 2016, at 14:39, David Smith <shmish...@gmail.com> wrote: >>>>> >>>>> 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 supposed to be >>>>> closed if 2 heartbeats were missed? >>>>> >>>>> Thanks. >>>>> >>>>> On Thu, Apr 14, 2016 at 12:31 PM, Michael Klishin <mklis...@pivotal.io >>>>> > wrote: >>>>> >>>>>> 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 a topic in >>>>>> the Google Groups "clojure-rabbitmq" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/clojure-rabbitmq/Z39EavO9Eas/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, 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. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to a topic in the >>>>> Google Groups "clojure-rabbitmq" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/clojure-rabbitmq/Z39EavO9Eas/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, 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. >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "clojure-rabbitmq" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/clojure-rabbitmq/Z39EavO9Eas/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, 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. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "clojure-rabbitmq" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/clojure-rabbitmq/Z39EavO9Eas/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, 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. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "clojure-rabbitmq" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojure-rabbitmq/Z39EavO9Eas/unsubscribe > . > To unsubscribe from this group and all its topics, 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.
