[
https://issues.apache.org/jira/browse/AMQ-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Corsi closed AMQ-3577.
------------------------------
Resolution: Fixed
This issue was fixed in trunk by Tim on the 29th of Oct.
The commit is
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQConnection.java?r1=1195044&r2=1195045&;.
He applied the same scheme that I was using to resolve the issue.
Note that the InvalidClientIDException was a symptom of this.
> 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
