http://www.nabble.com/Duplicate-messages-sent-to-Queue-after-broker-restarts-tp15598179p25443652.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
View this message in context:
http://www.nabble.com/Duplicate-messages-sent-to-Queue-after-broker-restarts-tp15598179p25441398.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
have you resolved this issue? I'm having the same issue. Any help would be
appreciated.
--
View this message in context:
http://www.nabble.com/Duplicate-messages-sent-to-Queue-after-broker-restarts-tp15598179p25440677.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
size = 0 right before I
bounce the broker.
So AFAICT the messages have been acknowledged and the transactions have been
committed, but the messages are redelivered as soon as the broker comes back
up.
--
View this message in context:
http://www.nabble.com/Duplicate-messages-sent-to-Queue-after
ryarger wrote:
I am running the 5.1 SNAPSHOT from 2/19 (have also used 2/12) and I am
noticing that messages are being resubmitted to queues after a broker
restart.
I have tried persisting to both the AMQ Store and to SQL Server. The issue
occurs for both.
I am using Spring's DefaultMessageListen
sages that were just processed
are sent again.
At first I suspected that I had something misconfigured, but the exact same
code works fine with AMQ 5.0.0.
Any ideas would be helpful.
Thanks.
--
View this message in context:
http://www.nabble.com/Duplicate-messages-sent-to-Queue-after-b
