Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10387

CLONE - Duplicate message detection causes message loss in cluster

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • EAP_EWP 5.2.0 ER5
    • EAP_EWP 5.2.0 ER4
    • HornetQ
    • None
    • Not Required
    • NEW

    Description

      Description is not for EAP 5.2.0.ER4. Taken from JBPAPP-10296 for EAP 6.0.1.ER3:

      Test scenario:
      1. Start two EAP 6.0.1.ER3 servers in cluster
      2. Deploy queue InQueue on both of the nodes
      3. Sent 50 messages with set "_HQ_DUPL_ID" message property to first node to InQueue
      4. Receive them from first node

      Result:
      Only 25 messages is received. The rest is discarded by first node 1:

      ...
      12:18:47,192 WARN  [org.hornetq.core.postoffice.impl.PostOfficeImpl] (Old I/O server worker (parentId: 954216388, [id: 0x38e02fc4, /192.168.40.1:5445])) Duplicate message detected - message will not be routed. Message information:ServerMessage[messageID=247,priority=4, bodySize=2413,expiration=0, durable=true, address=jms.queue.InQueue,properties=TypedProperties[{_HQ_ROUTE_TO=[B@70c7c57c, count=36, _HQ_DUPL_ID=47f14971-0337-439f-a157-977b6547e3051351595922925}]]@1266059708
      12:18:47,193 WARN  [org.hornetq.core.postoffice.impl.PostOfficeImpl] (Old I/O server worker (parentId: 954216388, [id: 0x38e02fc4, /192.168.40.1:5445])) Duplicate message detected - message will not be routed. Message information:ServerMessage[messageID=250,priority=4, bodySize=2413,expiration=0, durable=true, address=jms.queue.InQueue,properties=TypedProperties[{_HQ_ROUTE_TO=[B@534cbc58, count=38, _HQ_DUPL_ID=1b329abf-7691-461c-872c-89fa48ad2d491351595922941}]]@1390501921
      12:18:47,193 WARN  [org.hornetq.core.postoffice.impl.PostOfficeImpl] (Old I/O server worker (parentId: 954216388, [id: 0x38e02fc4, /192.168.40.1:5445])) Duplicate message detected - message will not be routed. Message information:ServerMessage[messageID=253,priority=4, bodySize=2413,expiration=0, durable=true, address=jms.queue.InQueue,properties=TypedProperties[{_HQ_ROUTE_TO=[B@4a6e4109, count=40, _HQ_DUPL_ID=a37ba36b-3a89-41a5-8a51-f59a847ac48c1351595923002}]]@208657420
      ...
      

      Attached reproducer:
      1. Download and unzip reproducer.zip
      2. Prepare servers - "sh prepare.sh" - this creates two servers with deployed jms/queue/InQueue
      3. Start first and second server:
      sh start-server1.sh <first_ip>
      sh start-server2.sh <second_ip>
      4. Start producer:
      sh start-producer.sh <first_ip>
      5. Start consumer:
      sh start-consumer.sh <first_ip>

      Attachments

        Issue Links

          Activity

            People

              csuconic@redhat.com Clebert Suconic
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: