Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2079

Too many instances of "duplicate message ... from cursor"

    Details

    • Steps to Reproduce:
      Hide

      Use unit test provided in attachment junit-duplicate-message.tgz . Simply unzip and run mvn clean test and wait for the above warning to occur many times.
      This unit test starts 100 producers and 10 consumers all producing to / consuming from the same queue.

      Show
      Use unit test provided in attachment junit-duplicate-message.tgz . Simply unzip and run mvn clean test and wait for the above warning to occur many times. This unit test starts 100 producers and 10 consumers all producing to / consuming from the same queue.
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      configure KahaDB with concurrentStoreAndDispatchQueues="false"

      Show
      configure KahaDB with concurrentStoreAndDispatchQueues="false"

      Description

      In a high throughput scenario on a single destination there can be many warnings of this kind:

      [2017-03-21 09:51:37,548] WARN ActiveMQ BrokerService[localhost] Task-5 Queue - queue://TEST, subscriptions=10, memory=102%, size=399, 
      pending=0, duplicate message ActiveMQTextMessage {commandId = 72, responseRequired = true, 
      messageId = ID:Mac.fritz.box-64479-1490086286066-183:1:1:1:68, originalDestination = null, originalTransactionId = null, 
      producerId = ID:Mac.fritz.box-64479-1490086286066-183:1:1:1, destination = queue://TEST, transactionId = null, expiration = 0, 
      timestamp = 1490086297427, arrival = 0, brokerInTime = 1490086297427, brokerOutTime = 1490086297427, correlationId = null, replyTo = null, persistent = true, 
      type = null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, 
      content = org.apache.activemq.util.ByteSequence@8672edc, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 50216, properties = null, 
      readOnlyProperties = false, readOnlyBody = false, droppable = false, jmsXGroupFirstForConsumer = false, text = ...XXXXXXXXXXXX} 
      from cursor, is cursor audit disabled or too constrained? Redirecting to dlq
      

      The broker loads messages twice into the cursor.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                garytully Gary Tully
                Reporter:
                mielket Torsten Mielke
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: