[jboss-jira] [JBoss JIRA] Assigned: (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=all ]

Gavin King reassigned JBAS-4481:
--------------------------------

    Assignee: Adrian Brock  (was: Gavin King)

Adrian, can you check an additional case.

Our blog site when down today because of the following case:

A transaction failed while accessing the database:

com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'STRING_VALUE' at row 1
       at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2939)
       at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1623)
       at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1715)
       at com.mysql.jdbc.Connection.execSQL(Connection.java:3249)
       at com.mysql.jdbc.PreparedStatement.executeInternal(Prepared

And (I believe) the tx was marked ROLLEDBACK. Subsequent attempts to begin() new transaction on the same thread failed.

What should be the expected behavior of the appserver transaction in this case?


> 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: Adrian Brock
>            Priority: Blocker
>             Fix For: JBossAS-4.2.1.GA
>
>         Attachments: test4481.tar
>
>
> 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