]
Pete Muir updated JBSEAM-3063:
------------------------------
Priority: Critical (was: Major)
Need to Swallow/WARN the IllegalStateException on STATUS_ROLLEDBACK
or STATUS_ROLLING_BACK
------------------------------------------------------------------------------------------
Key: JBSEAM-3063
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3063
Project: Seam
Issue Type: Bug
Components: Core
Reporter: Samuel Mendenhall
Priority: Critical
Fix For: 2.1.0.BETA1, 2.0.3.CR1
"STATUS_MARKED_ROLLBACK is a bit more of a pain since it basically involves a race
where the reaper thread may rollback the tx between Seam checking the status and rolling
it back via the business thread. Thus it's not possible to tell if the exception is
legit and needs to be reported to the app, or if it's a result of the reaper having
got there first. Given that most of the interesting failures will throw something other
than IllegalStateException it's probably reasonable to log it at WARN rather than
rethrowing it.
You can tell if the reaper is rolling back a tx by looking for something along the lines
of 'terminating transaction with multiple thread active in it' in the logs, or run
with tx debug logging on and the reaper will report which tx it's rolling back in
detail. "
"Right, so the fix would appear to be just to change the exception handling behavior
of Seam so that if the tx is STATUS_ROLLEDBACK or STATUS_ROLLING_BACK it swallows the
IllegalStateException thrown by rollback() "
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: