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

(7.0.z) Exception coming from a transaction resource has to be provided to client when transaction failure occurs on server

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Critical
    • None
    • 7.1.0.DR15
    • Transactions

    Description

      The problematic scenario is following

      1. a client server starts a transaction and call other server with the txn context
      2. the other server makes some actions (resources are enlisted and some work is done)
      3. the client server calls prepare/commit for ejb remoting resource pointing on the other server
      4. the other server tries to prepare/commit its subordinate transaction but it fails

      • a resource has a trouble and throws an exception
        5. server should pack the txn exception and put there the exception that was thrown by resource
        5. the client server should see the exception, exception cause and suppressed exceptions
        (suppressed exceptions contains the exception thrown by client)

      This behavior is expected by customer (see https://bugzilla.redhat.com/show_bug.cgi?id=1435549)

      This case is follow-up to JBEAP-7957

      Attachments

        Issue Links

          clones

          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-9993 (7.1.0) 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.
          • Verified
          is blocked by

          Feature Request - Feature requests from customers and/or users JBEAP-10437 (7.0.z) (Narayana) 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.
          • Resolved

          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

          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
          relates to

          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-7958 [GSS] (7.0.z) JBTM-2822 - Add suppressed exceptions for failures during prepare

          • 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.
          • Verified

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: