[jbossts-issues] [JBoss JIRA] Commented: (JBTM-575) javax.transaction.RollbackException root cause

[Mark Little (JIRA)]

    [ https://jira.jboss.org/browse/JBTM-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534018#action_12534018 ] 

Mark Little commented on JBTM-575:
----------------------------------

"First mark the transaction for rollback and then throw the exception. I am not aware of what the JTA spec mandates for a situation when both setRollbackOnly is called on the TransactionManager and an exception is also thrown by a beforeCompletion() method."

It can't happen. If you call setRollbackOnly then the two-phase commit protocol doesn't get triggered, so beforeCompletion won't be called.

> javax.transaction.RollbackException root cause
> ----------------------------------------------
>
>                 Key: JBTM-575
>                 URL: https://jira.jboss.org/browse/JBTM-575
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JTA
>    Affects Versions: 4.7.0
>         Environment: JBoss 5.1.0.GA
>            Reporter: Richard Kennard
>
> In JBoss 4.2.3.GA and previous releases, when a transaction rolled back the RollbackException included the root cause of the exception. This enhancement was implemented in response to JBAS-4238 and JBTM-66.
> However, in JBoss 5.1.0.GA this enhancement has been lost in some scenarios. This does not affect manual debugging (the root cause is still logged higher up in the logs), but makes it difficult for application code that relies on being able to unwrap the RollbackException to determine its root cause and therefore take appropriate action.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira