Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 26 Jan 2012 22:19:40 +0000 (UTC)
From: "Timothy Bish (Resolved) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <625060747.83037.1327616380442.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1068209760.82971.1327614704425.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (AMQ-3683) Enhance the InactivityMonitor shutdown
 logic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish resolved AMQ-3683.
-------------------------------

    Resolution: Fixed

Fix applied in trunk
                
> Enhance the InactivityMonitor shutdown logic
> --------------------------------------------
>
>                 Key: AMQ-3683
>                 URL: https://issues.apache.org/jira/browse/AMQ-3683
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Trivial
>             Fix For: 5.6.0
>
>
> The read and write check methods in AbstractInactivityMonitor should be checking the monitorStarted value to ensure that they don't attempt to execute unnecessary read and write check events into the ASYNC_TASKS executor.  The effect of the extra checks during shutdown doesn't break anything but can result in a longer time to shutdown the transport and more logging for no reason.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira