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/11 00:34:20 UTC

[jira] [Resolved] (AMQCPP-487) CMS FailoverTransport Leaks Socket Descriptors

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

Timothy Bish resolved AMQCPP-487.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 3.8.0
                   3.7.1

fixed on trunk and in 3.7.x
                
> CMS FailoverTransport Leaks Socket Descriptors
> ----------------------------------------------
>
>                 Key: AMQCPP-487
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-487
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.6.0
>            Reporter: Kevin Urciolo
>            Assignee: Timothy Bish
>             Fix For: 3.7.1, 3.8.0
>
>
> See the discussion by following the link below.
> http://activemq.2283324.n4.nabble.com/CMS-3-6-Socket-Descriptor-Leak-With-Failover-td4667966.html
> The FailoverTransport.cpp taskRunner includes the FailoverTransport and CloseTransports tasks.  The FailoverTransport is added first, and appears to always be pending.  This means the taskRunner always executes the iterate on the FailoverTransport and the CloseTransports tasks are never run, which causes a build up of socket descriptors (and threads).
> We worked around the issue by adding the CloseTransportsTask to the taskRunner first.  This allows the CompositeTaskRunner to iterate the CloseTransportsTask when there is work, and then switching back to iterating the FailoverTransport.

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