camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hanson <>
Subject Re: Necessity of transactional JMS component
Date Mon, 09 May 2011 15:15:55 GMT
So can I summarize as below?

1) TX and redelivery are not necessarily got introduced into a route at the
same time;

2) In TX case, an explicit TransactionErrorHandler is not needed either.

During a network failure(or any error) the transaction is immediately rolled
back. Furthermore, can I configure the next trial interval?

3) In redelivery case, the redelivery policy can be precisely configured.
But if the program shut down abnormally, the in-flight message must get
lost, because they are not persisted or returned to the message consumer.


Java for food, Python for fun
View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message