[jbossts-issues] [JBoss JIRA] Commented: (JBTM-575) javax.transaction.RollbackException root cause
[
https://jira.jboss.org/jira/browse/JBTM-575?page=com.atlassian.jira.plugi...
]
Jonathan Halliday commented on JBTM-575:
----------------------------------------
Hi Richard
This does not make much sense to me. JBAS-4238 and JBTM-66 are similar but not equivalent.
The JBAS issue is addressed in both releases, but JBossAS 4.2.3 uses TS 4.2.3.SP7, which
does not have the JBTM-66 changes. JBossTS AS 5.1.0.GA uses TS 4.6.1.GA , which does. So,
you seem to be having problems due to a behaviour change that you requested in the first
place?! Ah well, maybe I misunderstood what you wanted. Do you have any preference
between the implementation alternatives I outline in
http://community.jboss.org/message/515473 assuming either will address your needs?
javax.transaction.RollbackException root cause
----------------------------------------------
Key: JBTM-575
URL: https://jira.jboss.org/jira/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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira