The problem that was fixed was the result of messages being
acknowledged incorrectly for batches - which can happen when
optimized acknowledges are used.
This sounds like a different issue then - could you set debug logging
to true for the broker (in the log4j.properties file) , do your test
again and send us the log?
cheers,
Rob
On 23 Apr 2006, at 15:21, rtselvan wrote:
Rob, I tried with the Apr 22 SNAPSHOT and still the messages are
redelivered.
At this point I am doubting that my code or confguration may be wrong.
Is there a timeout value that causing the broker to resend the message
again. Interestingly the messages are redelievered after the MDB
completes
the processing of the messages (even though it took a long time to
complete). But the messages are not redelievered when the MDB
completes
quickly.
Any thoughts? I am also thinking that I could write code to handle the
duplicate messages (some work) but it is not clean as the activemq
handling
that.
thanks
--
View this message in context: http://www.nabble.com/Messages-get-
redelivered-more-than-once-t1478185.html#a4051102
Sent from the ActiveMQ - User forum at Nabble.com.
