[
https://issues.apache.org/jira/browse/OOZIE-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3289:
--------------------------------
Summary: TestJMSAccessorService#testConnectionRetry is still flaky (was:
Test TestJMSAccessorService#testConnectionRetry is still flaky)
> TestJMSAccessorService#testConnectionRetry is still flaky
> ---------------------------------------------------------
>
> Key: OOZIE-3289
> URL: https://issues.apache.org/jira/browse/OOZIE-3289
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Attachments: OOZIE-3289-001.patch
>
>
> TestJMSAccessorService#testConnectionRetry can still fail with the following
> error:
> {noformat}
> 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)
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
