Understanding ActiveMQ Inactivity timeout monitor in STOMP

[xabhi]

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=&quot;mqbrokerTcpNioTransport&quot; 
                                   
uri=&quot;nio://0.0.0.0:61616?&lt;b>wireFormat.maxInactivityDuration=120000&*amp;maximumConnections=600&amp;wireFormat.maxFrameSize=157286400"
                                   
maximumProducersAllowedPerConnection="200"
                                   
maximumConsumersAllowedPerConnection="200" />
     
            <amq:transportConnector name="mqbrokerStompNioTransport" 
                                   
uri="stomp+nio://0.0.0.0:61613?maximumConnections=100&amp;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.