[jboss-jira] [JBoss JIRA] (WFWIP-86) [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge

[Justin Bertram (JIRA)]

    [ https://issues.jboss.org/browse/WFWIP-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616379#comment-13616379 ] 

Justin Bertram commented on WFWIP-86:
-------------------------------------

bq. Ok, was with EAP 7.1 against EAP 7.1?

Yes.  I just changed the test to use containers 1 & 2 rather than 1 & 3.  Nothing else was changed.

{noformat}
diff --git a/jboss-hornetq-testsuite/common-tests/src/test/java/org/jboss/qa/hornetq/test/bridges/JMSBridgeTestCase.java b/jboss-hornetq-testsuite/common-tests/src/test/java/org/jboss/qa/hornetq/test/bridges/JMSBridgeTestCase.java
index c2304e768..fb7911b7b 100644
--- a/jboss-hornetq-testsuite/common-tests/src/test/java/org/jboss/qa/hornetq/test/bridges/JMSBridgeTestCase.java
+++ b/jboss-hornetq-testsuite/common-tests/src/test/java/org/jboss/qa/hornetq/test/bridges/JMSBridgeTestCase.java
@@ -243,7 +243,7 @@ public class JMSBridgeTestCase extends HornetQTestCase {
     public void testStartStopJMSBridge() throws Exception {
 
         Container inServer = container(1);
-        Container outServer = container(3);
+        Container outServer = container(2);
 
         prepareServers(inServer, outServer, Constants.QUALITY_OF_SERVICE.ONCE_AND_ONLY_ONCE);
         outServer.start();
{noformat}

> [Artemis 2.x upgrade] Duplicated messages in scenario with stop/start JMS bridge
> --------------------------------------------------------------------------------
>
>                 Key: WFWIP-86
>                 URL: https://issues.jboss.org/browse/WFWIP-86
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis
>            Reporter: Miroslav Novak
>            Assignee: Martyn Taylor
>            Priority: Blocker
>
> There are duplicated messages in scenario where JMS bridge is stopped and started.
> Test Scenario:
> * Start 2 servers and configure JMS from node-1 to node-3
> * Start sending messages to queue InQueue to  node-1
> * Stop JMS bridge using management operation (CLI)
> * Wait for 5 sec
> * Start JMS bridge using management operation
> * Start receiving mesage from node-3 from OutQueue
> Expected results:
> There are no lost/duplicated mesages. 
> Actual Result:
> Receiver got duplicated messages. 
> Link to failed Jenkins run:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-weekly-compatibility-journal-and-jms-bridge/36/EAP_VERSION_OLD=7.1.0.GA,jdk=oracle-java-1.8,os=RHEL7&&large&&dynamic/



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)