Claus, my questions are really specific to how Camel wraps the underlying AMQ technologies. In particular, how Camel handles transactions and client acknowledgements when exceptions are raised and redelivery policies applied (using Camel's onException clause, etc).
Also, I'm not running in DUPS_OK mode explicitly (using AUTO_ACK mode). But this seems to be the behavior that I'm seeing... On another note, I did purchase the "Camel In Action" pre-release (which I see you are an author of) but haven't found much on this specific topic yet. Will subsequent chapters will cover this? thanks again... Claus Ibsen-2 wrote: > > 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. > > ----- Ben - Senior Consultant -- View this message in context: http://old.nabble.com/guaranteed-message-processing-question...-tp26202573p26270070.html Sent from the Camel - Users mailing list archive at Nabble.com.
