Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <22947735.1197836246935.JavaMail.jira@brutus>
Date: Sun, 16 Dec 2007 12:17:26 -0800 (PST)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1518) NetworkConnector is leaking a thread if
 broker disconnects
In-Reply-To: <16735508.1197649407575.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Rob Davies resolved AMQ-1518.
-----------------------------

    Resolution: Fixed

Fixed by revision 604689

> NetworkConnector is leaking a thread if broker disconnects
> ----------------------------------------------------------
>
>                 Key: AMQ-1518
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1518
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: use MessageBroker 5.0.0.5, Windows, using NetworkConnector with duplex set to true
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.1.0
>
>
> Consider the following scenario: Two brokers A and B. Broker B sets up a NetworkConnector to Broker A using a static URL list and setting duplex ="true" (see attached configuration). At runtime Broker B will correctly connect to Broker A. jconsole shows a NetworkBridge being set up.
> For every network bridge that gets set up, three threads get started in Broker A, e.g:
> VMTransport: vm://localhost#5
> ActiveMQ Transport: tcp://host:4533
> ActiveMQ Connection Dispatcher: /host:4533
> Now, when Broker B disconnects, the network bridge will be closed down and the above threads need to cleaned up. The first two threads do get closed correctly, however the Connection Dispatcher thread stays alive and does not get closed. We are leaking this thread!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.