Thanks for the response Christian. I have been reading through the Camel in Action and ActiveMQ in Action books most of the day today. I'm starting to get a better understanding of how transactions work and that definitely seems like the way to go. Also, seems like the DLQ and transactions work together, so that I can dump off messages in the DLQ if "something bad happens". I think what I want in my case is to set up the redelivery policy so that messages stay on the queue until the cxfrs endpoint becomes available again. Looks like I can achieve this with a value of -1 for the maximumRedelivery configuration. I just need to determine a good balance for the other settings (i.e. redeliveryDelay) so that I'm not trashing the system by constantly trying to resend messages to an unavailable endpoint.
Can someone tell me what the useCollisionAvoidence setting is for? The only explanation that I can find is: "Should the redelivery policy use collision avoidance" This really isn't telling me a whole lot. I can't seem to find anything in either book that discusses it either. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Transacted-vs-DeadLetterQueue-tp5713992p5714032.html Sent from the Camel - Users mailing list archive at Nabble.com.
