You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Torsten Mielke (JIRA)" <ji...@apache.org> on 2017/06/12 07:31:01 UTC
[jira] [Created] (AMQ-6700) Leak of "ActiveMQ Connection Executor"
threads and ActiveMQConnection objects in JCA
Torsten Mielke created AMQ-6700:
-----------------------------------
Summary: Leak of "ActiveMQ Connection Executor" threads and ActiveMQConnection objects in JCA
Key: AMQ-6700
URL: https://issues.apache.org/jira/browse/AMQ-6700
Project: ActiveMQ
Issue Type: Bug
Components: JCA Container, RAR
Affects Versions: 5.14.5
Environment: JCA
Reporter: Torsten Mielke
Assignee: Torsten Mielke
The ActiveMQ JCA layer may leak threads of name {{"ActiveMQ Connection Executor"}} and instances of {{org.apache.activemq.ActiveMQConnection}} when there are problems with establishing the connection.
If the initial openwire connection cannot be established, it may run an "ActiveMQ Connection Executor" thread to deal with the error leading to a code path that does not close the connection and does not clear up the "ActiveMQ Connection Executor" thread.
Low level details in further comments.
This problem can be reproduced by running {{ActiveMQResourceAdapter.TransactionContext.recover()}} but potentially other code paths in the resource adapter are effected as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)