[
https://jira.jboss.org/jira/browse/JBAS-3633?page=com.atlassian.jira.plug...
]
Jason T. Greene updated JBAS-3633:
----------------------------------
Fix Version/s: Unscheduled
(was: 6.0.0.M3)
Unscheduling due to inactivity. Reassign to a release that you feel comfortable resolving
this issue in, or leave as is.
Tidyup logging when transaction is no longer active
---------------------------------------------------
Key: JBAS-3633
URL:
https://jira.jboss.org/jira/browse/JBAS-3633
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transaction Manager (Arjuna)
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Assignee: Jonathan Halliday
Priority: Minor
Fix For: Unscheduled
Since JBossTM rollsback transactions at transaction timeout,
we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly,
etc)
such that the logging is more information and not so noisy.
We still need to communicate that the transaction rolled back even if it is not
the transaction demarcation point that does the rollback.
Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback,
because the transaction is already ended.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira