Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CA04517F4F for ; Wed, 18 Mar 2015 10:10:39 +0000 (UTC) Received: (qmail 93363 invoked by uid 500); 18 Mar 2015 10:10:39 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 93289 invoked by uid 500); 18 Mar 2015 10:10:39 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 93006 invoked by uid 99); 18 Mar 2015 10:10:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2015 10:10:39 +0000 Date: Wed, 18 Mar 2015 10:10:39 +0000 (UTC) From: "Nelson Correia (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQCPP-568) CMS FailoverTransport Leaks Socket Descriptors with secondary backup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQCPP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson Correia updated AMQCPP-568: ---------------------------------- Regression: Regression > 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 > Environment: OS: Sun OS sun4v sparc, SUNW, Netra-T5440 > 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)