This was an issue with the 5.1 version. It has been resolved in the 5.3
snapshots.
I don't believe it was fixed in in 5.2. But we never used 5.2, so I am not
100% sure.
We worked around the issue by deleting the data directory before bringing
the broker back up.
Hope that helps.
-Rich
--
View
The DefaultMessageListenerContainer is supposed to handle the commit for you,
but I did try manually committing the session and I was still able to
reproduce the issue.
I have also confirmed that both the AMQ admin web page and the jconsole show
these messages as having been dequeued and a queue
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 DefaultMessageListenerContainer for
