On 10/21/2015 02:15 PM, mbroadst wrote: > Hi, > I'm a maintainer for a node.js amqp 1.0 module (node-amqp10), and we have a > user currently facing issues connecting to an ActiveMQ instance. It seems > that when our client sends our default idle timeout of 120000ms in the > initial open performative, ActiveMQ is not honoring that value. ActiveMQ > does seem to "agree" to the terms, and sends back 120000ms back in the > corresponding handshake Open performative, but then appears to expect > heartbeat (or flow) messages every 30s (which I gather is the default). Is > this is a bug, or are we missing something during the handshake? > > Thanks, > Matt > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-does-not-seem-to-honor-the-agreed-upon-idle-time-out-tp4703244.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > The broker and client don't "agree" on timeouts, the broker will send the idle timeout value it wants the client to honor, and the client will send it's requirements to the broker. By default the broker Idle timeout is set to 30s so it will request the client to send a heartbeat at half that interval.
You should start capturing some frame traces between client and broker which should give you some more clarity on what is going on. -- Tim Bish Sr Software Engineer | RedHat Inc. [email protected] | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
