[jboss-jira] [JBoss JIRA] Commented: (JBAS-4481) Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread

[Gavin King (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-4481?page=comments#action_12365144 ] 
            
Gavin King commented on JBAS-4481:
----------------------------------

"If a timeout goes off, the transaction will be rolled back by a separate thread but it cannot (not required to by the standards) do thread-to-transaction disassociation. What the original creating thread should do is find out the transaction has rolled back (e.g., when it tries to do some other work within the transaction it'll get an exception), and do a rollback anyway. That is the only way you can guarantee to get the thread-to-transaction association changed."

This is totally absurd. Are you serious?

The transaction is Status.ROLLEDBACK, and the application should call rollback() on it? What a ridiculous assertion.

Besides, UNDER NO CIRCUMSTANCES should ANY request to the application server POSSIBLY create a circumstance where the application server must be restarted before it can serve other requests.

Stop making excuses and fix this clearly broken behavior.


> Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4481
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4481
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.2.0.GA
>            Reporter: Gavin King
>         Assigned To: Jonathan Halliday
>            Priority: Blocker
>             Fix For: JBossAS-4.2.1.CR1
>
>
> If a transaction timeout occurs, the UserTransaction object does not get cleaned up from the thread, even after the request ends and the thread returns to the pool. Future requests will not be able to begin() a transaction, since the STATUS_ROLLEDBACK UserTransaction throws this exception:
> Caused by: javax.transaction.NotSupportedException
> 	at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.begin(BaseTransaction.java:79)
> 	at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.begin(BaseTransactionManagerDelegate.java:77)
> 	at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.begin(ServerVMClientUserTransaction.java:124)
> 	at org.jboss.seam.transaction.UTTransaction.begin(UTTransaction.java:29)
> This means that any transaction timeout that occurs will leave the application server in a permanently broken state and require a server restart. Hence 4.2.0.GA is currently unusable in production!
> This needs to be fixed in an immediate patch release.

-- 
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