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

Enhance behavior of transaction propagation called over IIOP to not start 2PC when called ejb creates own new transaction

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Obsolete
    • Minor
    • None
    • 7.1.0.DR1
    • EJB, IIOP
    • None

    Description

      Based on discussion at jira JBEAP-5126 (https://issues.jboss.org/browse/JBEAP-5126?focusedCommentId=13271878#comment-13271878) there could be a good enhancement for transaction propagated over ejb called over iiop to not start 2PC process when the called ejb creates its own new transaction (TransactionAttributeType.REQUIRES_NEW).

      Quoting Tom's comment here

      Yeah, its expected to be this way for JTS as the context is propagated
      over. It could be possible to register an enhancement in the iiop
      subsystem to remove the context from the thread if the EJB does not
      require a propagated transaction.

      Attachments

        Issue Links

          is cloned by

          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) WFLY-6920 Enhance behavior of transaction propagation called over IIOP to not start 2PC when called ejb creates own new transaction

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open
          is related to

          Feature Request - Feature requests from customers and/or users JBEAP-5126 Prevent enlisting additional resources on EJB caller side in case of server side RequiresNew

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: