[
https://issues.apache.org/activemq/browse/AMQ-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies reassigned AMQ-1596:
-------------------------------
Assignee: Rob Davies
> In 5.1-SNAPSHOTs, duplicate messages sent after broker restart
> --------------------------------------------------------------
>
> Key: AMQ-1596
> URL: https://issues.apache.org/activemq/browse/AMQ-1596
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: Windows and Linux
> Reporter: Richard Yarger
> Assignee: Rob Davies
> Fix For: 5.3.0
>
> Attachments: AMQJiraTicket.zip
>
>
> I am seeing duplicate messages delivered after bouncing the broker.
> I have seen it happen in 5.1 SNAPSHOTS on 2/12 and 2/19.
> It does not occur in 5.0.0.
> I have persisted to both AMQ Store and to SQL Server.
> It occurs for both.
> Simple test flow:
> 1) Start the broker.
> 2) Start the consumer (running in Spring DefaultMessageListenerContainer)
> 3) Run the producer, which sends 5 new messages.
> 4) Messages are consumed.
> Both the admin web app and jconsole show the messages as dequeued and a queue
> size of 0.
> 5) Bounce the broker.
> 6) The messages are resent to the consumer.
> Spring's DefaultMessageListenerContainer is supposed to automatically
> acknowledge and commit the session transaction,
> but I have tried manual acks and commits as well.
> I am still able to reproduce.
> I have broken down my code to the simplest test case that can reproduce the
> issue.
> I am including this code and my broker config file.
> Have I configured something incorrectly or is there an issue in 5.1?
> Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
