[
https://jira.jboss.org/jira/browse/JBTM-575?page=com.atlassian.jira.plugi...
]
Bozhidar Batsov commented on JBTM-575:
--------------------------------------
Johathan, can I ask you another question on a related topic(one that does not involve the
client at all).
If a business method in EJB session bean throws a RuntimeException in the JBoss log I see
only this line:
11:32:12,550 ERROR [TxPolicy] javax.ejb.EJBTransactionRolledbackException
No cause, no message, no nothing - the RuntimeException is however successfully relayed to
the client, but I remember that in older JBoss version I used to
get I full stack trace with the javax.ejb.EJBTransactionRolledbackException. What might be
causing this problem?
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