Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10437

(7.0.z) (Narayana) Provide way of getting suppressed exceptions out of SubordinateTransaction

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 7.0.10.GA
    • None
    • Transactions
    • None

    Description

      We need to provide way how to pass suppressed exceptions of of the `SubordinateTransaction` to the caller.

      This request came from customer case and https://bugzilla.redhat.com/show_bug.cgi?id=1435549 as we need to provide exceptions thrown from transaction resource.

      The interface is used for controlling propagated transaction from one server to another in EAP/WFLY.

      Callers are is ejb3 subsystem in EAP 6.4/7.0 and WFTC in EAP 7.1.

      Attachments

        Issue Links

          blocks

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-10011 (7.0.z) Exception coming from a transaction resource has to be provided to client when transaction failure occurs on server

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          clones

          Feature Request - Feature requests from customers and/or users JBTM-2870 Provide way of getting suppressed exceptions out of SubordinateTransaction

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10417 (7.0.z) Upgrade JBoss Transaction Manager from 5.2.22 to 5.2.24

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              spyrkob Bartosz Spyrko-Smietanko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: