Duplicate messages sent in Active MQ 5.7

[badrinana]

I upgraded Active MQ from 5.5 to 5.7. My producer application sent a message
to active mq queue at 12:04:11 PM as shown below.

INFO:[2013/12/03 12:04:11.002 PM MessageListener process] Message ->
ActiveMQTextMessage {commandId = 5, responseRequired = true, messageId =
ID:A-53212-1386090245809-0:0:1:1:1, originalDestination = null,
originalTransactionId = null, producerId = ID:A-53212-1386090245809-0:0:1:1,
destination = queue://Input, transactionId = null, expiration = 0, timestamp
= 1386090250166, arrival = 0, brokerInTime = 1386090250859, brokerOutTime =
1386090250998, correlationId = null, replyTo = null, persistent = true, type
= null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
null, compressed = false, userID = null, content = null,
marshalledProperties = org.apache.activemq.util.ByteSequence@67d6b87e,
dataStructure = null, redeliveryCounter = 0, size = 0, properties =
{POSSIBLE_DUP=false, TID=11429970}, readOnlyProperties = true, readOnlyBody
= true, droppable = false, text = <Data xmlns =&quot;......&lt;/Data>}

Restart Active MQ around 12:22. My consumer receives the same message after
restart. I checked the producer log to see if it re-sent this message again.
The producer did not resend the message to the queue.

INFO:[2013/12/03 12:22:34.716 PM MessageListener process] Message ->
ActiveMQTextMessage {commandId = 5, responseRequired = true, messageId =
ID:A-53212-1386090245809-0:0:1:1:1, originalDestination = null,
originalTransactionId = null, producerId = ID:A-53212-1386090245809-0:0:1:1,
destination = queue://Input, transactionId = null, expiration = 0, timestamp
= 1386090250166, arrival = 0, brokerInTime = 1386090612998, brokerOutTime =
1386091354610, correlationId = null, replyTo = null, persistent = true, type
= null, priority = 4, groupID = null, groupSequence = 0, targetConsumerId =
null, compressed = false, userID = null, content = null,
marshalledProperties = org.apache.activemq.util.ByteSequence@41a80e5a,
dataStructure = null, redeliveryCounter = 0, size = 0, properties =
{POSSIBLE_DUP=false, TID=11429970}, readOnlyProperties = true, readOnlyBody
= true, droppable = false, text = <Data xmlns =&quot;.......&lt;/Data>}

I have 2 brokers running as master/slave configuration. The 1st broker
connects to database while 2nd broker waits to acquire lock on the database.

Can you please let me know if any configuration can be done to avoid this
scenario? I am not doing enableAudit or optimizeAcknowledge.

Appreciate your help!



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Duplicate-messages-sent-in-Active-MQ-5-7-tp4675063.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.