activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3683) Enhance the InactivityMonitor shutdown logic
Date Thu, 26 Jan 2012 22:19:40 GMT

     [ 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

        

Mime
View raw message