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

LRA timeout test failure because of "wedged" ReaperElement

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 5.11.3.Final
    • LRA, Testing
    • None
    • Hide

      The failure is time sensitive and difficult to reproduce. Perhaps just running the test many times could trigger it (maybe also load the system while running the test:

       

       mvn test -Dtest=LRATest#testTimeout -f rts/lra/coordinator/pom.xml

       

      Show
      The failure is time sensitive and difficult to reproduce. Perhaps just running the test many times could trigger it (maybe also load the system while running the test:   mvn test -Dtest=LRATest#testTimeout -f rts/lra/coordinator/pom.xml  

    Description

      The fix for JBTM-3533 uses the TransactionReaper to manage LRA timeouts.

      A new test was added for the work (LRATest.java#testTimeout) where the participant sleeps for longer than the LRA timeout (to verify that the reaper cancels the LRA).

      However, this test was seen to fail on a CI run (on a pull request) because the reaper reported the the participant (a ReaperElement) as "wedged" (see attached test output file). The reason is as follows:

      The reaper sees it as wedged because the participant is running in the same VM as the test and the participant sleeps (Thread.sleep(2000)) to allow time for the timeout to expire. So this test failure is actually a false positive because the reaper reinserts the element into the timeout queue marking it as ABORT_ONLY and since LongRunningAction extends BasicAction it handles the ActionStatus.ABORT_ONLY state correctly.

       

      The tests needs updating to accommodate this race condition.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3538 TCK timeout test failure fix

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBTM-3533 Use TransactionReaper to manage LRA timeouts

          • 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

              rhn-engineering-mmusgrov Michael Musgrove
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: