I am experiencing a similar issue.
When a consumer of a queue fails to acknowledge() a message, getting a
queuebrowser instance and calling
getEnumeration() is causing all the messages that are unacknowledged to be
redelivered.
This is a distinct change in behavior from 4.1.1 to 5.1.0. In 4.1.1,
On 8 May 2008, at 22:02, BlueFox wrote:
I just did some more checking, turns out it is the QueueBrowser that
is
causing the duplicate message problem. I have a QueueBrowser that
uses the
following code to periodically verify the queue size and perform
verification after queue size is zero
I just did some more checking, turns out it is the QueueBrowser that is
causing the duplicate message problem. I have a QueueBrowser that uses the
following code to periodically verify the queue size and perform
verification after queue size is zero.
private static class JMSBrowser implements Ses
