Diego Dupin added a comment - 2024-07-04 09:54 to be honest, this has not been done, because there were no explaination about this option and very few documentation. It will be done in 3.x branch now, and with proper documentation.

Diego Dupin added a comment - 2024-07-04 10:53 Just curious, but didn't you have issue with 2.x implementation as well ? It seems to me that CONJ-122 was doing only half the job.

Gregor Balthasar added a comment - 2024-07-05 09:12 This is great news, we are looking forward to it! Probably you are right, we tried so much lately that I got a little bit confused. We never used the 2.x implementation but started with 3.1.4 as it was part of Spring Boot 2.x and 3.1.4 did not work either. Then I wondered if the parameter did do nothing and found the upgrade document which stated it to be gone. In the meantime we upgraded to Spring Boot 3.x which brings 3.3.3 so i based this ticket on it.

Gregor Balthasar added a comment - 2024-07-08 12:16 Hi, thanks for the quick resolving of this issue! Any chance for getting a nightly build via sonatype anytime soon so we could test this in our environment? Many thanks, Gregor

Diego Dupin added a comment - 2024-07-08 12:28 this is available throught snapshot using : <repositories> <repository> <id>sonatype-nexus-snapshots</id> <name>Sonatype Nexus Snapshots</name> <url>https: //oss.sonatype.org/content/repositories/snapshots</url> </repository> </repositories>   <dependencies> <dependency> <groupId>org.mariadb.jdbc</groupId> <artifactId>mariadb-java-client</artifactId> <version> 3.4 . 1 -SNAPSHOT</version> </dependency> </dependencies>

Gregor Balthasar added a comment - 2024-07-08 14:17 - edited Unfortunately, this is not solving our problem yet. Now we get the same error from the newly introduced 'MariaDbPoolPinnedConnection': 2024 - 07 -08T16: 10 : 56.330 + 02 : 00 WARN 14647 --- [ main] c.a.datasource.xa.XAResourceTransaction : XA resource 'xaDataSource' : resume for XID 'XID: 3139322E3136382E3137382E3130302E746D313732303434373633313234303030303032:3139322E3136382E3137382E3130302E746D31' raised - 5 : invalid arguments were given for the XA operation   javax.transaction.xa.XAException: null at org.mariadb.jdbc.MariaDbPoolConnection.mapXaException(MariaDbPoolConnection.java: 180 ) ~[mariadb-java-client- 3.4 . 1 - 20240708.122651 - 3 .jar:na] at org.mariadb.jdbc.MariaDbPoolPinnedConnection$MariaDbXAPinnedResource.execute(MariaDbPoolPinnedConnection.java: 69 ) ~[mariadb-java-client- 3.4 . 1 - 20240708.122651 - 3 .jar:na] at org.mariadb.jdbc.MariaDbPoolPinnedConnection$MariaDbXAPinnedResource.start(MariaDbPoolPinnedConnection.java: 166 ) ~[mariadb-java-client- 3.4 . 1 - 20240708.122651 - 3 .jar:na] at com.atomikos.datasource.xa.XAResourceTransaction.resume(XAResourceTransaction.java: 217 ) ~[transactions-jta- 6.0 . 0 -jakarta.jar:na] at com.atomikos.datasource.xa.session.BranchEnlistedStateHandler.<init>(BranchEnlistedStateHandler.java: 40 ) ~[transactions-jta- 6.0 . 0 -jakarta.jar:na] at com.atomikos.datasource.xa.session.NotInBranchStateHandler.checkEnlistBeforeUse(NotInBranchStateHandler.java: 46 ) ~[transactions-jta- 6.0 . 0 -jakarta.jar:na] at com.atomikos.datasource.xa.session.TransactionContext.checkEnlistBeforeUse(TransactionContext.java: 58 ) ~[transactions-jta- 6.0 . 0 -jakarta.jar:na] at com.atomikos.datasource.xa.session.SessionHandleState.notifyBeforeUse(SessionHandleState.java: 165 ) ~[transactions-jta- 6.0 . 0 -jakarta.jar:na] at com.atomikos.jdbc.internal.AtomikosJdbcConnectionProxy.enlist(AtomikosJdbcConnectionProxy.java: 88 ) ~[transactions-jdbc- 6.0 . 0 -jakarta.jar:na] at com.atomikos.jdbc.internal.AtomikosJdbcConnectionProxy.updateTransactionContext(AtomikosJdbcConnectionProxy.java: 61 ) ~[transactions-jdbc- 6.0 . 0 -jakarta.jar:na] at com.atomikos.jdbc.internal.AbstractJdbcConnectionProxy.prepareStatement(AbstractJdbcConnectionProxy.java: 64 ) ~[transactions-jdbc- 6.0 . 0 -jakarta.jar:na] I did some digging and debugging and the chain of executes is like: START <ID>, END <ID>, START<ID> -> Exception -> Rollback. I am not sure why END is called while just staying in the same transaction and performing multiple readonly DB selects via Hibernate while in Atomikos XA transaction environment. As stated before, the same code using the mysql-connector-j driver addressing the same MariaDB database is working just fine. Best regards, Gregor PS: I just debugged the mysql-connector-j 'SuspendableXAConnection' and found that it changes the 'TMJOIN' flag at the START command to a 'TMRESUME' flag. Maybe this is what is causing the error we are getting now since afaik neither Mysql nor MariaDB support the JOIN command.

Diego Dupin added a comment - 2024-07-10 10:40 ah, yes this is missing. https://github.com/mariadb-corporation/mariadb-connector-j/commit/f68447f17a14461642415167d93f21cfc6ebaed4 added. 3.4.1-SNAPSHOT version updated. Could you confirm the correction ?

Gregor Balthasar added a comment - 2024-07-10 12:05 This is doing the trick! Our whole test suite now runs without errors now with 3.4.1-snapshot. We really appreciate your work, with 3.4.1 we can then switch back to mariadb-connector-j which is great news for us. Many thanks again and hopefully 3.4.1 is released soon Best regards, Gregor