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

Wrong Transaction behaviour for EJBs if JTS is enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.ER3, 7.1.0.ER1
    • 7.0.0.ER2 (Beta)
    • 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

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-3801 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.
          • Closed

          Activity

            People

              fedor.gavrilov Fedor Gavrilov (Inactive)
              fedor.gavrilov Fedor Gavrilov (Inactive)
              Daniel Simko Daniel Simko (Inactive)
              Daniel Simko Daniel Simko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: