Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <17340914.1174432654646.JavaMail.jira@brutus>
Date: Tue, 20 Mar 2007 16:17:34 -0700 (PDT)
From: "Jan K (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Closed: (AMQ-1211) Connections are not being properly
 disposed of.
In-Reply-To: <23738352.1174432234469.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-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan K closed AMQ-1211.
----------------------

    Resolution: Fixed

Created a new issue where the Broker was specified as a component

> Connections are not being properly disposed of.
> -----------------------------------------------
>
>                 Key: AMQ-1211
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1211
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>         Environment: Latest  trunk version (As of March 20, 2007) of AMQ .NET client, windows 2000 (for the broker)
>            Reporter: Jan K
>            Priority: Critical
>
> The connection pool on the broker grew until no more connections could be made.  I did notice, that the connections that were supposed to have been disposed, have their ConnectionId set to 'Unavailable' when viewed using JConsole. That was the only difference between truly active connections and ones that should have been closed.
> For now, we have fixed it by going back to 4.0.2. 

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