[
https://issues.jboss.org/browse/WFLY-3443?page=com.atlassian.jira.plugin....
]
Jesper Pedersen updated WFLY-3443:
----------------------------------
Issue Type: Task (was: Bug)
IJ doesn't "close" the connection - the connection is destroyed, as it is
now unsafe to use
JCA "tracking" should default to false
--------------------------------------
Key: WFLY-3443
URL:
https://issues.jboss.org/browse/WFLY-3443
Project: WildFly
Issue Type: Task
Security Level: Public(Everyone can see)
Components: JCA
Reporter: Scott Marlow
Assignee: Stefano Maestri
Fix For: 9.0.0.Alpha1
The [
txtracking|http://www.ironjacamar.org/doc/roadto12/txtracking.html] feature is
causing failures when IronJacamar closes the database connection in a
Synchronization.afterCompletion() when a Hibernate Synchronization.afterCompletion() call
already closed the connection.
See attached server.log for example of "IJ000315: Pool cts-derby-pool has 1 active
handles" error.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)