Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10258

Prevent enlisting additional resources on EJB caller side in case of server side @RequiresNew

    XMLWordPrintable

Details

    Description

      Scenario:

      • server-1 (intermediary)
        • Running standalone profile
        • Has a remote-outbound-connection pointing at server-2 through server-2's public IP address
        • Intermediary bean need to lookup the Target bean in server-2 and also inject the TransactionManager
        • Intermediary bean need to enlist a dummy XAResource
      • server-2 (target)
        • disable JBOSS-LOCAL-USER auth
        • Target bean needs to be annotated with @REQUIRES_NEW (important)
      • Standalone EJB client invokes an intermediary bean server-1, which as a result invokes target bean on server-2.

      The dummy XAResource should log in the commit method whether one-phase optimization is being used like:

          @Override
    public void commit(Xid arg0, boolean onePhaseOptim) throws XAException {
        logger.info("-- Committing in the client resource. One-phase optimisation is: " + onePhaseOptim + " --"
                + (onePhaseOptim ? "" : " -> TWO-PHASE COMMIT !!!"));
    }

      In this scenario it is expected that the one-phase optimization is being used!

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14638 [GSS](7.1.z) 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
          relates to

          Feature Request - Feature requests from customers and/or users JBTM-3020 Add ability for resources to indicate XA_RDONLY on end

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

          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) WFTC-47 Introduce ordered interposed synchronization facility

          • 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.
          • Pull Request Sent

          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) WFTC-46 Add provider utilities for safe rollback/suspend

          • 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.
          • Pull Request Sent

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: