Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-66

"Already marked for rollback" Exception could include original cause

    XMLWordPrintable

Details

    • Feature Request
    • Status: Closed (View Workflow)
    • Optional
    • Resolution: Done
    • 4.2
    • 4.6.0
    • JTA
    • None
    • Low

    Description

      First up, thank you for providing such a wondefully stable implementation! I have a small feature request:

      At present whenever a, say, SFSB throws a RuntimeException, JTA goes into 'rollback' mode. From then on, anyone who tries to do any further work (including when the SessionContext tries to remove the rolled back SFSB) will trigger a different RuntimeException saying, in short, 'Already marked for rollback'.

      It would be very helpful if the 'Already marked for rollback' Exception could include, as its getCause (which is standard as of JDK 1.4), the original exception that started off the rollback? At present we are often left with the situation where all the original caller gets back is a 'Already marked for rollback' Exception, and there is no way to 'drill down' to find what the original cause was.

      Of course, you could also argue that the SessionContext should be smarter about trying to remove rolled back EJBs.

      Attachments

        Activity

          People

            rhn-engineering-jhallida Jonathan Halliday
            kenrod_jira kenrod (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1 week
                1w
                Remaining:
                Remaining Estimate - 1 week
                1w
                Logged:
                Time Spent - Not Specified
                Not Specified