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

Wrong Transaction behaviour for EJBs if JTS is enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 11.0.0.Final
    • 8.1.0.Final
    • EJB
    • None
    • Hide

      A reproducer project is attached.

      • use 'standalone.sh -c standalone-full.xml
      • run the enableJTS : jboss-cli.sh -c --file=enableJTS.cli
      • deploy target/ejb30-jpa.jar
      • run
      • java -cp JB/bin/client/jboss-client.jar:target/test-classes:target/classes org.jboss.wfink.ejb30.StatefulRemoveMain
      • java -cp JB/bin/client/jboss-client.jar:target/test-classes:target/classes org.jboss.wfink.ejb30.StatelessMain
      Show
      A reproducer project is attached. use 'standalone.sh -c standalone-full.xml run the enableJTS : jboss-cli.sh -c --file=enableJTS.cli deploy target/ejb30-jpa.jar run java -cp JB/bin/client/jboss-client.jar:target/test-classes:target/classes org.jboss.wfink.ejb30.StatefulRemoveMain java -cp JB/bin/client/jboss-client.jar:target/test-classes:target/classes org.jboss.wfink.ejb30.StatelessMain

    Description

      If JTS is enabled the invocation of EJB's might show a arjuna warning for each method invocation:
      WARN [com.arjuna.ats.jts] (RequestProcessor-5) ARJUNA022261: ServerTopLevelAction detected that the transaction was inactive
      This is only the case if other resources are involved, i.e. a DB via JPA.
      If a simple bean is used (like ejb-remote quickstart) this warning is not shown.

      It looks like the transaction is local commited but in case of a SFSB @Remove method the result is a " WFLYEE0006: Failed to destroy component instance Instance of SFTestBean" and the lifecycle method @PreDestroy is not invoked.

      Attachments

        1. 456a624-withDestroy.log
          662 kB
        2. 8d49872-error.log
          676 kB
        3. enableJTS.cli
          0.7 kB
        4. reproducer.zip
          29 kB
        5. server.log
          48 kB

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13681 [GSS](7.2.0) Default SFSB Lifecycle methods transaction attribute causing warnings

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13682 [GSS](7.1.z) Default SFSB Lifecycle methods transaction attribute causing warnings

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-9509 Default SFSB Lifecycle methods transaction attribute causing warnings

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13689 [GSS](7.0.z) Default SFSB Lifecycle methods transaction attribute causing warnings

          • 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.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11846 Wrong Transaction behaviour for EJBs if JTS is enabled

          • 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
          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) WFLY-4002 avoid arjuna "detected that the transaction was inactive" warnings from org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization.afterCompletion

          • 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

              sdouglas1@redhat.com Stuart Douglas
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: