Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 6 Jun 2013 19:13:20 +0000 (UTC)
From: "Karen Morrissey (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12650892.1370357845833.80364.1370546000078@arcas>
In-Reply-To: <JIRA.12650892.1370357845833@arcas>
References: <JIRA.12650892.1370357845833@arcas>
Subject: [jira] [Resolved] (AMQ-4569) Stomp inactivity timeout takes
 significantly longer than specified
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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: 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