no-pool and xa-transaction with no caching result in connections being closed
before the tx ends.
-------------------------------------------------------------------------------------------------
Key: GERONIMO-2688
URL: http://issues.apache.org/jira/browse/GERONIMO-2688
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: connector
Affects Versions: 1.1.1, 1.2, 2.0
Reporter: David Jencks
Assigned To: David Jencks
Fix For: 2.0
A user has discovered that a connection manager for an outbound resource
adapter configured for no-pool and xa-transaction (with no caching) results in
the physical connection being closed before the transaction can be completed.
This might possibly be a problem with pooling enabled if there's a long delay
between the connection handle being closed and the transaction ending, during
which time the idle remover might fire up and remove the connection.
This problem can be worked around by enabling transaction-caching which keeps
the connection associated with the transaction until the transaction ends
(preventing it from being closed) or by enabling thread-caching (which ties the
connection to the thread more or less indefinitely, and has not really been
tested ever).
I'll think about whether it is practical to fix this directly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
