TransactionManager - error in delist; already committed
patrickvankann Aug 23, 2004 4:59 AMI'm getting a transaction-related problem where the TransactionManager claims that my container managed transaction is "already committed" during delist(). The transaction seems to commit just fine and data gets updated in my database - and the error only shows on the console and in the log.
I am having trouble debugging this problem because I cannot see the full stack-trace of the nested exception. I have turned on debugging in the TransactionManager as described in READ THIS FIRST but the full stack of the root cause of the exception is not being shown. Below is the edited log message - I want to be able to see the extra lines after "...67 more". If anyone can help me to be able to see the full stack trace I would be most grateful - and any clues as to what might be causing the underlying exception would also be most excellent! Thanks everyone.
06,519 TRACE [org.jboss.tm.TransactionImpl] Committing, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=socks//15, BranchQual=], status=STATUS_ACTIVE
2004-08-19 18:05:06,519 TRACE [org.jboss.tm.TransactionImpl] calling sync 0, org.exolab.castor.jdo.engine.DatabaseImpl@10d78ec:cookietime
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] calling sync 1, org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener$TxRemover@12929b2
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] Before completion done, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=socks//15, BranchQual=], status=STATUS_ACTIVE
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] endresources(0): state=1
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] endResource(XidImpl [FormatId=257, GlobalId=socks//15, BranchQual=1]) entered: org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@f44031 flag=67108864
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] endResource(XidImpl [FormatId=257, GlobalId=socks//15, BranchQual=1]) leaving: org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@f44031 flag=67108864
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] One phase commit: One resource.
2004-08-19 18:05:06,529 TRACE [org.jboss.tm.TransactionImpl] Committing resources, resourceStates[0]=3
2004-08-19 18:05:06,569 TRACE [org.jboss.tm.TransactionImpl] delistResource(): Entered, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=socks//15, BranchQual=] status=STATUS_COMMITED
2004-08-19 18:05:06,569 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2004-08-19 18:05:06,569 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2004-08-19 18:05:06,569 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2004-08-19 18:05:06,569 ERROR [org.jboss.resource.connectionmanager.TxConnectionManager] Error while closing connection handle!
org.jboss.resource.JBossResourceException: Error in delist!; - nested throwable: (java.lang.IllegalStateException: Already committed.)
... [etc etc - some extraneous lines deleted here...]
Caused by: java.lang.IllegalStateException: Already committed.
at org.jboss.tm.TransactionImpl.delistResource(TransactionImpl.java:529)
at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.delist(TxConnectionManager.java:486)
... 67 more