-
Bug
-
Resolution: Done
-
Major
-
7.0.0.GA
java.lang.AssertionError: expected:<FAILURE_DETECTED> but was:<FAILOVER_FAILED> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.apache.activemq.artemis.tests.integration.jms.cluster.JMSFailoverListenerTest.testManualFailover(JMSFailoverListenerTest.java:228)
I found out that problem is in [1]. When events occur consecutive, ordering of their executions is not guaranteed.
[1]
ActiveMQConnection.java
private static class FailoverEventListenerImpl implements FailoverEventListener { private final WeakReference<ActiveMQConnection> connectionRef; FailoverEventListenerImpl(final ActiveMQConnection connection) { connectionRef = new WeakReference<ActiveMQConnection>(connection); } @Override public void failoverEvent(final FailoverEventType eventType) { ActiveMQConnection conn = connectionRef.get(); if (conn != null) { try { final FailoverEventListener failoverListener = conn.getFailoverListener(); if (failoverListener != null) { new Thread(new Runnable() { public void run() { failoverListener.failoverEvent(eventType); } }).start(); } } catch (JMSException e) { if (!conn.closed) { ActiveMQJMSClientLogger.LOGGER.errorCallingFailoverListener(e); } } } } }
- blocks
-
JBEAP-2574 Stabilization of ActiveMQ Artemis upstream test suite
- Closed
- is cloned by
-
JBEAP-5981 (7.0.z) [Artemis Testsuite] JMSFailoverListenerTest#testManualFailover fails
- Closed
- is incorporated by
-
JBEAP-6523 (7.1.0) Upgrade Artemis to 1.5.0
- Closed
- cloned to
-
ARTEMIS-538 Loading...