-
15. Re: commit timeout but data lost
Think about this way... if you are sending a message only... you just use duplicate detection and always resend your message on failure.
as for receiving, you definitely need XA. Maybe we can think of an alternative (even if it's outside of the JMS api), but that will be a feature.
I have seeing some users coupling with failures on their own way. (like doing something on their app)
ATM the way to go with any JMS provider is XA. (at least that I'm aware of).
That should be an edge case BTW. You shouldn't be having as many failures on connection. If you are.. you should probably fix that and treat connection failures on commit a real edge case.
-
16. commit timeout but data lost
Clebert Suconic wrote:
ATM the way to go with any JMS provider is XA. (at least that I'm aware of).
Beware of too smart TransactionManager, though. If the JMS provider would be the only XAResource used in the transaction, an optimalization could occur which would call single phase commit() instead of two phase prepare() and commit(). Make sure that this optimalization would be disabled in this case.
-