See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/changes
See https://builds.apache.org/job/ActiveMQ/changes
[
https://issues.apache.org/jira/browse/AMQ-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102545#comment-13102545
]
Luigi R. Viggiano commented on AMQ-3104:
I had the same problem in production.
[
https://issues.apache.org/jira/browse/AMQ-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102545#comment-13102545
]
Luigi R. Viggiano edited comment on AMQ-3104 at 9/12/11 11:07 AM:
Thanks for the report. It looks like we are at least leaking threads on the
InactivityMonitor. I've taken the sample provided and used it as a base to
reproduce the problem. I can reproduce a thread leak for every connection
that should have been cleaned up via Dispose(). I'll take a closer
Upgrade to Camel 2.8.1
--
Key: AMQ-3494
URL: https://issues.apache.org/jira/browse/AMQ-3494
Project: ActiveMQ
Issue Type: Task
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Priority: