You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/06/05 00:07:20 UTC
[jira] [Commented] (AMQ-4569) Stomp inactivity timeout takes
significantly longer than specified
[ https://issues.apache.org/jira/browse/AMQ-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13675330#comment-13675330 ]
Timothy Bish commented on AMQ-4569:
-----------------------------------
You can further debug the inactivity monitor by setting these values for the AMQ logging which will show you the monitor checking the client.
{noformat}
log4j.logger.org.apache.activemq.transport=TRACE
{noformat}
You should see something along these lines.
{noformat}
2013-06-04 18:02:09,204 [0.1:33780@51836] - DEBUG StompInactivityMonitor - Stomp Inactivity Monitor read check: 5000, write check: 0
2013-06-04 18:02:09,205 [0.1:33780@51836] - DEBUG ProtocolConverter - Stomp Connect heartbeat conf RW[5000,0]
2013-06-04 18:02:09,205 [ ReadCheckTimer] - TRACE AbstractInactivityMonitor - A receive is in progress
2013-06-04 18:02:14,206 [ ReadCheckTimer] - DEBUG AbstractInactivityMonitor - 5001 ms elapsed since last read check.
2013-06-04 18:02:14,206 [ ReadCheckTimer] - TRACE AbstractInactivityMonitor - A receive is in progress
2013-06-04 18:02:19,206 [ ReadCheckTimer] - DEBUG AbstractInactivityMonitor - 5000 ms elapsed since last read check.
2013-06-04 18:02:19,206 [ ReadCheckTimer] - TRACE AbstractInactivityMonitor - Message received since last read check, resetting flag:
2013-06-04 18:02:24,206 [ ReadCheckTimer] - DEBUG AbstractInactivityMonitor - 5000 ms elapsed since last read check.
2013-06-04 18:02:24,206 [ ReadCheckTimer] - DEBUG AbstractInactivityMonitor - No message received since last read check for tcp:///127.0.0.1:33780@51836. Throwing InactivityIOException.
2013-06-04 18:02:24,210 [yMonitor Worker] - DEBUG AbstractInactivityMonitor - Running ReadCheck[tcp://127.0.0.1:33780]
{noformat}
> 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
>
>
> 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