activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Camel generating message with correlationid=null and tmp-queue null
Date Mon, 02 Apr 2018 03:32:45 GMT
I just realized that the OP seems to have created a new thread about the
same issue at
http://activemq.2283324.n4.nabble.com/Inactivity-Monitor-closing-connection-exactly-at-given-timeout-even-keepalive-true-td4738132.html,
so I'm abandoning this one unless he replies with information that's
relevant to this thread specifically.

Tim

On Sun, Apr 1, 2018 at 9:19 PM, Tim Bain <tbain@alumni.duke.edu> wrote:

---------- Forwarded message ----------
> From: <mallarajes@gmail.com>
> Date: Thu, Mar 29, 2018 at 5:44 PM
> Subject: Re: Camel generating message with correlationid=null and
> tmp-queue null
>
> 3) for the inactivity monitor : thank you for advising the cause of
> disconnection. we have overriden org.apache.activemq.transport.
> http.HttpTransportFactory.compositeConfigure()
> and creating InactivityMonitor same as like super class only difference is
> we have overriden onException. This code is proper.
> but main observation is, whatever setConnectAttemptTimeout we have set,
> after that exactly it is disconnecting even useKeepAlive is true.
> is this the behaviour of inactivity monitor ? actually it should close
> connection only when there is inactivity, still it is closing connection
> even if it is active
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message