[jboss-jira] [JBoss JIRA] Commented: (JBAS-4481) Transaction timeouts leave garbage Status.ROLLEDBACK UserTransaction object bound to the thread
[ http://jira.jboss.com/jira/browse/JBAS-4481?page=comments#action_12377782 ]
Adrian Brock commented on JBAS-4481:
------------------------------------
Gavin
1) This issue is closed. If you have the issue with 4.2.1 then raise a new bug report.
RULE: We don't re-open issue in closed releases.
2) There are tests that show the problem was resolved. If the test doesn't cover your
case
then provide the information on how your case is different.
3) You posted a MySQL exception and an assertion, show the evidence not the assertion,
e.g. where are logs?
RULE: We don't guess what the problem is, nor do we trust blind assertion
4) The MySQL exception shows no JBoss stacktrace, how do I know the context? Is it web,
ejb2/3, etc.
RULE: One error message does not a bug report make
5) What version of JBoss does the blog site use? What is its configuration? e.g. Does it
have the valve
here the issue was fixed - see JBAS-4487?
RULE: How do we know you even have the fixed version?
THIS ISSUE IS OVERLY LONG AND USELESS ANYWAY. NO MORE COMMENTS HERE PLEASE
THE REAL ISSUE WHAT NOT THE GUESS WORK HERE IT WAS JBAS-4487
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