Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3111 [Umbrella] Fix flaky tests in Oozie
  3. OOZIE-3289

TestJMSAccessorService#testConnectionRetry is still flaky

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.1.0
    • None
    • None

    Description

      TestJMSAccessorService#testConnectionRetry can still fail with the following error:

      testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)  Time elapsed: 2.26 s  <<< FAILURE!
junit.framework.AssertionFailedError
        at junit.framework.Assert.fail(Assert.java:55)
        at junit.framework.Assert.assertTrue(Assert.java:22)
        at junit.framework.Assert.assertFalse(Assert.java:39)
        at junit.framework.Assert.assertFalse(Assert.java:47)
        at junit.framework.TestCase.assertFalse(TestCase.java:219)
        at org.apache.oozie.service.TestJMSAccessorService.testConnectionRetry(TestJMSAccessorService.java:168)

      Root cause: changes in connectionMap / receiversMap / retryConnectionsMap are not atomic. Could be that one map has been updated but another has not.

      Other tests could be affected, too.

      Attachments

        1. OOZIE-3289-001.patch
          3 kB
          Peter Bacsko

        Issue Links

          relates to

          Sub-task - The sub-task of the issue OOZIE-3292 Test TestJMSAccessorService#testConnectionRetryExceptionListener is still flaky

          • Major - Major loss of function.
          • Closed

          Activity

            People

              pbacsko Peter Bacsko
              pbacsko Peter Bacsko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: