Warn in AMQ:suppressing duplicate delivery on connection, poison acking

Solution Verified - Updated -

Issue

I got below warning in my consumer side. I want to know whether it is harmful or not.

14:58:12 WARN  ID:XX.XX.XX.XX-43691-1507790837739-1:1:1:1 suppressing duplicate delivery on connection, poison acking: MessageDispatch {commandId = 0, responseRequired = false, consumerId = ID:XX.XX.XX.XX-43691-1507790837739-1:1:1:1, destination = queue://queque.test, message = ActiveMQTextMessage {commandId = 6, responseRequired = false, messageId = ID:XX.XX.XX.XX-37267-1507791480409-1:1:1:1:1, originalDestination = null, originalTransactionId = null, producerId = ID:XX.XX.XX.XX-37267-1507791480409-1:1:1:1, destination = queue://queque.test, transactionId = TX:ID:XX.XX.XX.XX-37267-1507791480409-1:1:1, expiration = 0, timestamp = 1507791480593, arrival = 0, brokerInTime = 1507791480594, brokerOutTime = 1507791492268, 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@558080c0, marshalledProperties = org.apache.activemq.util.ByteSequence@5b477400, dataStructure = null, redeliveryCounter = 1, size = 0, properties = {property=XXXX message Property}, readOnlyProperties = true, readOnlyBody = true, droppable = false, jmsXGroupFirstForConsumer = false, text = topic message 0 Thu Oct 12 14:58:00 CST 2017}, redeliveryCounter = 1}

Environment

  • Red Hat JBoss AMQ 6.X

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In