Repository navigation
Keycloak 26.3.4 doesn't support DB without XA transactions? #42731
Unanswered
v-kamerdinerov
asked this question in
Q&A
Replies: 1 comment 5 replies
|
What you are seeing is not directly related to the XA enabled flag. XA enabled = false means to use a Connection via a DataSource, instead of an XADataSource. The stacktrace confirms the transaction manager is using a LocalXAResource which just wraps a Connection. The batch operation being performed may not be well supported in your setup. We just need to figure out where the problem lies. Can you try this scenario without the proxy? The broken pipe could be indicative of a problem there. |
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Has anyone tried running the latest vanilla keycloak (anything above major version 26 - specifically 26.3.4) alongside Galera (mariadb) as the database?
We previously used this setup on version 20, specifying
KC_TRANSACTION_XA_ENABLED: false, without any issues.Now I'm trying to deploy the latest version side-by-side on a clean database for testing, and I'm clearly running into these XA transactions.
I double-checked — my Galera/MariaDB version does not support XA transactions:
I'm running a keycloak instance in Kubernetes - I connect to the Galera DB via proxysql - here's my ENV (more details):
As you can see, I explicitly set:
And I still get this error: