Configuration from one transportConnector does not translate over to any other connector.
What does you STOMP client send in its CONNECT frame for the heart-beat value? What broker version are you running? On 11/24/2015 02:50 AM, xabhi wrote: > Hi, > > Below is my ActiveMQ configuration file. I have specified > wireFormat.maxInactivityDuration for TCP Nio transport. Does this inactivity > timeout applies to STOMP connector as well? > > I am seeing cases where if my STOMP client is busy for more than 5 mins in > doing some operation and doesn't send heartbeats, ActiveMQ closes that > connection. Does broker logs anything for indicating this timeout? > Another confusing thing is why does timeout happens only after 5 mins, if it > uses same inactivity value the timeout should happen after 2 mins, right? > > Could anyone please explain this behavior? > > > <amq:transportConnectors> > <amq:transportConnector name="mqbrokerTcpNioTransport" > > uri="nio://0.0.0.0:61616?<b>wireFormat.maxInactivityDuration=120000&*amp;maximumConnections=600&wireFormat.maxFrameSize=157286400" > > maximumProducersAllowedPerConnection="200" > > maximumConsumersAllowedPerConnection="200" /> > > <amq:transportConnector name="mqbrokerStompNioTransport" > > uri="stomp+nio://0.0.0.0:61613?maximumConnections=100&transport.maxDataLength=157286400" > > > maximumProducersAllowedPerConnection="200" > > maximumConsumersAllowedPerConnection="200" /> > </amq:transportConnectors> > > > Thanks, > Abhi > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Understanding-ActiveMQ-Inactivity-timeout-monitor-in-STOMP-tp4704227.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Tim Bish Sr Software Engineer | RedHat Inc. tim.b...@redhat.com | www.redhat.com twitter: @tabish121 blog: http://timbish.blogspot.com/
