activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Corsi (Commented) (JIRA)" <j...@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.
Date Thu, 03 Nov 2011 16:45:32 GMT

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

Claudio Corsi commented on AMQ-3577:
------------------------------------

Agreed, but this is caused by the client not properly handling an interrupted thread.  The
broker does not seem to get the request to close the connection which gives the broker the
impression that the connection is still active on the client side when in fact it was closed.

You can see the problem by just doing the following:

  1 - create a connection
  2 - interrupt the thread
  3 - close the connection
  4 - repeat 1-3 over and over

open the jconsole and check the thread count on the broker.  it keeps increasing until you
get an oom exception.

                
> 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

        

Mime
View raw message