Repository navigation
Support excluding additional datasources from JTA transaction management #52873
Replies: 2 comments
|
Thanks for the detailed writeup @takehana-ke. You're right that This looks like a reasonable, fairly contained enhancement. The per-datasource option plumbing ( Since this isn't just a question but a concrete feature proposal, could you open an enhancement issue using the feature request template so it can be tracked and prioritized? Feel free to link back to this discussion for context. |
Uh oh!
There was an error while loading. Please reload this page.
Since Keycloak 26.4.0, additional datasource settings can be configured using Keycloak options in
conf/keycloak.conf. However, there does not seem to be a supported Keycloak configuration option equivalent to:We use an additional PostgreSQL datasource only for read operations, so it does not need to participate in JTA transactions. Currently, the available Keycloak option is:
However, this only switches between XA and non-XA transactions. It does not provide a way to disable JTA transaction integration entirely. Could Keycloak provide a supported configuration option equivalent to:
This would allow read-only additional datasources to be excluded from JTA without relying on raw Quarkus properties.
This seems related to #30929, but this proposal is not about allowing multiple non-XA datasources in the same transaction. The intention is to exclude an additional datasource from JTA transaction management entirely.
Thank you for considering this.
All reactions