Skip to main content

[ejb-spec issues] [JIRA] Created: (EJB_SPEC-114) Allow discovery of rollback cause

  • From: "ljnelson (JIRA)" <jira-no-reply@...>
  • To: issues@...
  • Subject: [ejb-spec issues] [JIRA] Created: (EJB_SPEC-114) Allow discovery of rollback cause
  • Date: Wed, 11 Sep 2013 16:53:07 +0000 (UTC)
  • Auto-submitted: auto-generated

Allow discovery of rollback cause
---------------------------------

                 Key: EJB_SPEC-114
                 URL: https://java.net/jira/browse/EJB_SPEC-114
             Project: ejb-spec
          Issue Type: Improvement
    Affects Versions: Future version
            Reporter: ljnelson


It would be nice if one could find the cause of a transaction's being marked 
for rollback.

Currently one can ask an EJBContext if its rollback-only status has been set. 
 But while debugging one may not understand exactly why the transaction has 
rolled back.

Nine times out of ten the root cause is a {{RuntimeException}} of some kind 
that was thrown and either hidden or otherwise obscured.  What if 
{{EJBContext}} could give you this?  Something like 
{{EJBContext.getRollbackException()}} or something similar?  The idea would 
be that the exception in question is the reason that the transaction was 
marked for rollback.

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

        


[ejb-spec issues] [JIRA] Created: (EJB_SPEC-114) Allow discovery of rollback cause

ljnelson (JIRA) 09/11/2013

[ejb-spec issues] [JIRA] Commented: (EJB_SPEC-114) Allow discovery of rollback cause

ljnelson (JIRA) 09/11/2013
 
 
Close
loading
Please Confirm
Close