You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Jonathan S Fisher (Jira)" <ji...@apache.org> on 2019/08/29 16:49:00 UTC
[jira] [Commented] (TOMEE-2651) TomEE Does not Free JMS Connection
from Pool after Transaction Timeout
[ https://issues.apache.org/jira/browse/TOMEE-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918771#comment-16918771 ]
Jonathan S Fisher commented on TOMEE-2651:
------------------------------------------
RCA:
After the transaction times out, the AutoConnectionTracker was trying to call `transactionRegistry.getResource`. The Geronimo JTA adapter is especially aggressive and throws an exception. This causes the removal process to abort, leaving the connection in a used state. See mailing list for more details. http://tomee-openejb.979440.n4.nabble.com/JTA-JMS-Spec-question-connection-leakage-td4690100.html
> TomEE Does not Free JMS Connection from Pool after Transaction Timeout
> ----------------------------------------------------------------------
>
> Key: TOMEE-2651
> URL: https://issues.apache.org/jira/browse/TOMEE-2651
> Project: TomEE
> Issue Type: Bug
> Reporter: Jonathan S Fisher
> Assignee: Jonathan S Fisher
> Priority: Major
>
> See here for a project to reproduce this issue: https://github.com/exabrial/tomee-jms2-bug/tree/connection-pool-leak
> Essentially, if your transaction times out, you can't free the connection and it's permanently considered occupied. This eventually drains the pool of connections and tomee freezes.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)