alexkazan87 commented on PR #7454: URL: https://github.com/apache/camel/pull/7454#issuecomment-1108200415
> @davsclaus I change to use `Synchronization` to abort or commit at the end of exchange. please take a review. > > @orpiske I also do the changes with the kafka transaction IT test with your suggestions. > > @alexkazan87 it could work with JTA but as @davsclaus metioned above that if it involves some resources (SQL or JMS) which supports XA, then they would work in tandem. In some cases, if the JTA transaction manager fails to commit (during the 2PC processing), but kafka transaction has been committed before and there is no chance to rollback the change since it does not support JTA/XA spec. There is still a risk with the data consistency. As far as I know, it could use **LAST RESOURCE COMMIT OPTIMIZATION** to take the kafka transaction participant in the global JTA transaction. I think Narayana supports this **LRCO*** but I need more invesigation. Thank you very much! I really appreciate it. It would be determinant if you can manage it through Narayana. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
