Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2643

"number-of-application-rollbacks" statistic counted multiple times during single rollback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 5.3.2.Final
    • None
    • Transaction Core
    • None
    • Hide

      Deploy an EJB with @TransactionTimeout set to 1 second, and make an EJB method sleep for more then 1 second:

      @Stateless
@TransactionAttribute(TransactionAttributeType.REQUIRED)
@TransactionTimeout(value = 1, unit = TimeUnit.SECONDS)
public class GreeterEJB implements GreeterEJBLocal {
    public String sayHello(String name) throws Exception {
        Thread.sleep(3000);
        return "Hello " + name;
    }
}

      Run the EJB method and check the stats:

      /subsystem=transactions:read-resource(include-runtime=true)
      Show
      Deploy an EJB with @TransactionTimeout set to 1 second, and make an EJB method sleep for more then 1 second: @Stateless @TransactionAttribute(TransactionAttributeType.REQUIRED) @TransactionTimeout(value = 1, unit = TimeUnit.SECONDS) public class GreeterEJB implements GreeterEJBLocal { public String sayHello( String name) throws Exception { Thread .sleep(3000); return "Hello " + name; } } Run the EJB method and check the stats: /subsystem=transactions:read-resource(include-runtime= true )

    Description

      During transaction timeout, "number-of-application-rollbacks" stat is incremented twice. As a result, "number-of-application-rollbacks" can be higher then "number-of-aborted-transactions".

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4036 "number-of-application-rollbacks" statistic counted multiple times during single rollback

          • 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) JBEAP-2456 Transaction statistics screen troubles and unclarity

          • 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

              thofman Tomas Hofman
              thofman Tomas Hofman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: