[
https://issues.apache.org/jira/browse/AMQCPP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628442#comment-14628442
]
ASF subversion and git services commented on AMQCPP-568:
--------------------------------------------------------
Commit d73ae266b0d98328d8f65a4b844f0f5f0d64d19d in activemq-cpp's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-cpp.git;h=d73ae26 ]
https://issues.apache.org/jira/browse/AMQCPP-569
https://issues.apache.org/jira/browse/AMQCPP-568
More agressive cleanup of failed connect Transport instances to avoid an
ever increasing number of them being held until successful reconnect.
> CMS FailoverTransport Leaks Socket Descriptors with secondary backup
> --------------------------------------------------------------------
>
> Key: AMQCPP-568
> URL: https://issues.apache.org/jira/browse/AMQCPP-568
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.8.4
> Reporter: Nelson Correia
> Assignee: Timothy Bish
>
> I've configured the URI with failover and with 2 hosts:
> failover:(tcp://primary:61616,tcp://secondary:61616)?randomize=false
> Assume that secondary is not working, and the primary is shut downed. The CMS
> enters in failover mode and the number of threads and sockets starts to
> enlarge.
> When I use the URI only with the primary it works well. I think this issue is
> somehow related with the https://issues.apache.org/jira/browse/AMQCPP-487
> issue, but didn't figure out what is wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
