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 2011/03/30 21:28:05 UTC

[jira] [Resolved] (AMQCPP-358) FailoverTransport can peg CPU when connection attempts exceeds max and its waiting to be closed

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

Timothy Bish resolved AMQCPP-358.
---------------------------------

    Resolution: Fixed

fixed in trunk and 3.2.x fixes branch.

> FailoverTransport can peg CPU when connection attempts exceeds max and its waiting to be closed
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-358
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-358
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.2.5
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.2.6, 3.3.0
>
>
> While waiting for its parent to close it the FailoverTransport can peg the CPU in the case where a limit is set on reconnect attempts.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira