Hi Could you ask / search at the AMQ forum. The questions is now more related to messaging in general how to do reliable bridges. I remember there is also a QoS term (Quality of Service) which specified such as - duplicates allowed - at most one - etc.
Try to see if that can help, looks as if duplicates allowed is the kind of mode you run with. On Fri, Nov 6, 2009 at 8:27 PM, boday <bo...@vektrel.com> wrote: > > Claus, I am using persistent queues, but I purge them prior to each test. > > I've rerun this test multiple times and it does deliver the correct number > if no exceptions are thrown. Its only when the exception handling kicks in > that I end up with duplicates being delivered. > > Any other thoughts on this? What happens exactly when an exception is > thrown in a transacted route? > > Can someone verify if this scenario is correct? > > flow w/o exception... > > -message sent by InboundQ (external process) > -message received by Processor1 and marked as sent/waiting for ACK in > InboundQ > -message received by Processor2 > -message sent to finishedQueue > -ACK sent back to InboundMessage queue > -message is removed from InboundQ > > w/exception > > -message sent by InboundQ (external process) > -message received by Processor1 and marked as sent/waiting for ACK in > InboundQ > -message received by Processor2 (throws Exception) > -onException clause kicks in and retries Processor2 3 times > -if success, message sent to finishedQueue, ACK sent back to InboundQ > -if 3 failures reached, message sent to errorQueue, ACK send back to > InboundQ > -message is removed from InboundQ > > thanks in advance... > > > > > > Claus Ibsen-2 wrote: >> >> Hi >> >> Do you use persistent queues? Then make sure the queues are empty when >> testing. Maybe deleting the AMQ data folder before testing. >> > > > ----- > Ben - Senior Consultant > > -- > View this message in context: > http://old.nabble.com/guaranteed-message-processing-question...-tp26202573p26230870.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
