[
https://issues.apache.org/jira/browse/AMQ-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676027#comment-13676027
]
Timothy Bish commented on AMQ-4569:
-----------------------------------
In general it will take two read check cycles before the client gets booted,
however in your case since the client simply connects and then does nothing the
inactivity monitor has settled and it ends up taking a third cycle normally if
you client connected, and did some other interaction with the broker this
wouldn't happen.
> Stomp inactivity timeout takes significantly longer than specified
> ------------------------------------------------------------------
>
> Key: AMQ-4569
> URL: https://issues.apache.org/jira/browse/AMQ-4569
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.8.0
> Environment: Windows 7, JRE 7.
> Reporter: Karen Morrissey
> Priority: Minor
> Labels: heartbeat, inactivity, stomp
> Attachments: activemq.log, activemq.log, activemq.log
>
>
> When I specify a timeout using a connector like the following to get a
> 5-minute idle timeout
> {code:xml}
> <transportConnector name="stomp"
> uri="stomp://0.0.0.0:61613?transport.defaultHeartBeat=300000,0"/>
> {code}
> It takes 15 minutes for it to time out. I tried one previously at 900000 (15
> minutes), and it had not timed out after 35 minutes, when I had to leave.
> So, it appears the timeout takes 3 times longer than specified. I find it
> suspicious that there is a call somewhere I saw in the code that divides the
> timeout period by 3.
--
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
