[ https://issues.apache.org/jira/browse/AMQ-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675356#comment-13675356 ]
Timothy Bish commented on AMQ-3603: ----------------------------------- You'll need to produce some test that shows this to be the case. > STOMP 1.1 introduced the heartBeat header implemented by the inactivity > monitor, would be nice to have this option for stomp 1.0 > -------------------------------------------------------------------------------------------------------------------------------- > > Key: AMQ-3603 > URL: https://issues.apache.org/jira/browse/AMQ-3603 > Project: ActiveMQ > Issue Type: Improvement > Components: Transport > Affects Versions: 5.5.1 > Reporter: Gary Tully > Assignee: Gary Tully > Labels: inactivity, monitor, stomp > Fix For: 5.6.0 > > > Stomp 1.0 does not provide for an inactivity monitor. A client connect that > stays idle will remain active on the broker indefinitely. With 1.1, the > inactivity monitor has come into play in response to the heartBeat header. > For 1.0 clients we need a way to indicate that there is a default heartBeat > header, so a broker readTimeout and no expectation of a writeTimeout. > Providing a transport option for stomp like > {{stomp://0.0.0.0:0?transport.defaultHeartBeat=5000,0}} would be nice. In the > absence of a heartbeat header, as in the stomp 1.0 case, this default value > would cause an InactivityMonitor with readCheck of 500 to be installed on > each new broker stomp transport connection. > Any client that remains inactive for more than 5 seconds will have their > broker connection closed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira