[JBoss JIRA] Created: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
6:03 p.m.
TransactionLocal cannot be locked when transaction is marked rollback only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]
Adrian Brock updated JBAS-4675:
-------------------------------
Priority: Critical (was: Major)
I'm marking this as critical since there are a number of places that use
TransactionLocal that could fail in random ways due to this problem,
i.e. they expect to be able to lock the transaction[local] until the transaction no longer
exists.
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:26 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=comments#action_12375421 ]
Jonathan Halliday commented on JBAS-4675:
-----------------------------------------
This problem seems to exist because the locks are implemented using Synchronizations for
state storage and it's considered an error to register a Synchronization when the
transaction is not running. However, there is no longer any reason to use that
implementation, so I'll drop the Synchronizations in favor of something else and
remove the restriction.
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=comments#action_12375637 ]
Adrian Brock commented on JBAS-4675:
------------------------------------
There's an ant project on the parent task that reproduces the problem.
You need to look at the server.log for the DEBUG message about the IllegalStateException.
The patch has already been applied for the parent task, so it's just a case of getting
rid of the spurious warning
by fixing the TransactionLocalDelegate.
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=comments#action_12375643 ]
Jonathan Halliday commented on JBAS-4675:
-----------------------------------------
Thanks, I'll have a look at the test case.
The underlying tx engine does not allow Synchronizations to be registered on completed
transactions. Thus simply removing the status check from the TransactionLocalDelegate will
only cause the exception to be thrown from a different point in the code. I need to rip
out the Synchronizations we use to store lock state and use the more general Object
storage mechanism added to the TransactionImple for JTA 1.1 instead. It should still not
take long though.
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=comments#action_12375649 ]
Adrian Brock commented on JBAS-4675:
------------------------------------
It's ok to disallow transaction local delegate construction if the status is not
ACTIVE,
similar to you cannot create the synchronization.
It's NOT ok to disallow retrieval of the delegate if it is was previouslly allowed to
be constructed
(assuming the transaction hasn't completed - rollback, heuristic or otherwise).
It's virtually the same rules as transaction synchronization.
i.e. You register the synchronization, setRollbackOnly() and still the afterCompletion()
gets invoked.
I imagine this also affects the TransactionSynchronizationRegistry implementation of
JavaEE5
which has a simpler "TransactionLocal" put/getResource notion?
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]
Dimitris Andreadis reopened JBAS-4675:
--------------------------------------
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]
Dimitris Andreadis closed JBAS-4675.
------------------------------------
Fix Version/s: JBossAS-4.2.2.GA
(was: JBossAS-5.0.0.Beta3)
Resolution: Done
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-4.2.2.GA
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4675) TransactionLocal cannot be locked when transaction is marked rollback only
[ http://jira.jboss.com/jira/browse/JBAS-4675?page=all ]
Dimitris Andreadis closed JBAS-4675.
------------------------------------
Fix Version/s: (was: JBossAS-4.2.2.GA)
Resolution: Done
Closing this for 4.2.x. Created a different issue for AS5.
TransactionLocal cannot be locked when transaction is marked rollback
only
--------------------------------------------------------------------------
Key: JBAS-4675
URL: http://jira.jboss.com/jira/browse/JBAS-4675
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Transaction Manager
Affects Versions: JBossAS-4.2.1.GA
Reporter: Adrian Brock
Assigned To: Jonathan Halliday
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
Related to the parent issue, the proposed fix does not work in jboss-4.2.x because
the transaction local cannot be locked when the status is ABORT.
Here's the stacktrace of the error:
2007-09-05 17:50:44,899 DEBUG
[org.jboss.resource.connectionmanager.CachedConnectionManager] Unable to synchronize with
transaction
java.lang.IllegalStateException: Transaction not active
at
com.arjuna.ats.jbossatx.TransactionLocalDelegateImpl.lock(TransactionLocalDelegateImpl.java:119)
at
com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.lock(BaseTransactionManagerDelegate.java:200)
at org.jboss.tm.TransactionLocal.lock(TransactionLocal.java:120)
at
org.jboss.resource.connectionmanager.TransactionSynchronizer.lock(TransactionSynchronizer.java:223)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.getCloseConnectionSynchronization(CachedConnectionManager.java:550)
at
org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:315)
at
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:622)
at
org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266)
at
org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129)
You shouldn't be able to create a new delegate if the transaction is not active,
but you should be able to retrieve existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6051
days inactive
6077
days old
8 comments
3 participants
participants (3)
-
Adrian Brock (JIRA) -
Dimitris Andreadis (JIRA)
-
Jonathan Halliday (JIRA)