Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 3 Nov 2011 16:37:32 +0000 (UTC)
From: "Gary Tully (Commented) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1349817422.56295.1320338252395.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1349634262.56236.1320336812248.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3577) The Connection is not cleanup
 properly whenever the close method is called within a thread that was
 interrupted.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143292#comment-13143292 ] 

Gary Tully commented on AMQ-3577:
---------------------------------

note: internally the broker should not be calling interrupt unless it catches an interrupted exception. But is should be able to handle interrupted exceptions as the occur in normal processing and continue if necessary.
                
> The Connection is not cleanup properly whenever the close method is called within a thread that was interrupted.
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3577
>                 URL: https://issues.apache.org/jira/browse/AMQ-3577
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, JMS client
>    Affects Versions: 5.5.1
>         Environment: any environment.
>            Reporter: Claudio Corsi
>             Fix For: 5.6.0
>
>
> The connection close method does not properly clean up the connection on the broker.
> This is causing a memory leak on the broker because the connection is dangling.
> I have not confirmed that trying to call the close method within a non-interrupted thread will properly cleanup the connection after it was already called within an interrupted thread.
> I have a test case that reproduces this issue and a patch that corrects the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira