MessageIdList.java
Regards,
Ozan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-of-Brokers-Duplicate-message-add-attempt-rejected-tp3771301p3790910.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://fusesource.com
http
.nabble.com/file/n3790910/MessageIdList.java
MessageIdList.java
Regards,
Ozan
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-of-Brokers-Duplicate-message-add-attempt-rejected-tp3771301p3790910.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
/Network-of-Brokers-Duplicate-message-add-attempt-rejected-tp3771301p3776983.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
| Duplicate message add attempt rejected. Destination: Q1, Message id:
ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1003
WARN | Duplicate message add attempt rejected. Destination: Q1, Message id:
ID:MSGTEST02-56791-634499717928681758-1:0:1:1:1004
WARN | Duplicate message add attempt rejected
the
messages on both brokerA and brokerB, and vice versa.
My configuration works, but I keep getting the following kind of error in my
logs:
WARN | Duplicate message add attempt rejected. Message id:
ID:brokerA-59948-1269961367915-0:19:1:1:181
I've configured each activemq-5.3 server
Note that I have also tried this with a networkconnection on only brokerA,
connecting to brokerB, with duplex=true. I get the same duplicate message
error.
--
View this message in context:
http://old.nabble.com/Duplicate-message-add-attempt-rejected-tp28084188p28084393.html
Sent from
Solved the problem. This was a bug in release 5.3.0. Upgraded to 5.3.1 to
fix.
--
View this message in context:
http://old.nabble.com/Duplicate-message-add-attempt-rejected-tp28084188p28086403.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
