-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support use of JTA transaction ? #54
Labels
Comments
@scalajos Sounds good to me! /bounty $100 |
💎 $100 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-jdbc! Add a bounty • Share on socials
|
/attempt #54 |
@cacapouh: Reminder that in 7 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support use of JTA / XA transaction
JTA transactions have some strict threading constraint :
to be part of a JTA transaction, a jdbc action must execute within a thread already bound to a JTA transaction
More specifically:
Using blocking IO pool (eg blocking {...}) naively would prevent any use of the library in a JTA context (no way to set XA transaction in thread context of the blocking section)
Here 2 quick ideas I propose but you certainly will find much better ones
where customExecutor would provide a jdbc IO executor which thread is guaranteed to be bound to a JTA transaction
I understand these are very rough ideas but I really think supporting JTA/XA transactions would be a significant advantage for the library
Best regards
The text was updated successfully, but these errors were encountered: