activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karen Morrissey (JIRA)" <>
Subject [jira] [Resolved] (AMQ-4569) Stomp inactivity timeout takes significantly longer than specified
Date Thu, 06 Jun 2013 19:13:20 GMT


Karen Morrissey resolved AMQ-4569.

    Resolution: Not A Problem

This issue was based on a misunderstanding of the heartbeat. In normal operation it will take
two heartbeats for an idle connection to be cleared. In some cases, such as a client that
connects but does not read at all, it will take three heartbeats before the connection is
cleared. Consequently, I am resolving this issue as "not a problem."
> Stomp inactivity timeout takes significantly longer than specified
> ------------------------------------------------------------------
>                 Key: AMQ-4569
>                 URL:
>             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
> {code:xml}
> <transportConnector name="stomp" uri="stomp://,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:

View raw message