Skip to content
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

* fixed issue #CONJ-489 #106

Merged
merged 1 commit into from Jun 5, 2017
Merged

Conversation

fishermans
Copy link
Contributor

@fishermans fishermans commented Jun 4, 2017

This fixed issue CONJ-489.

Caused by: javax.transaction.xa.XAException: (conn:41252) You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '0x
at org.mariadb.jdbc.MariaXaResource.mapXaException(MariaXaResource.java:123)
at org.mariadb.jdbc.MariaXaResource.execute(MariaXaResource.java:137)
at org.mariadb.jdbc.MariaXaResource.start(MariaXaResource.java:314)
at com.atomikos.datasource.xa.XAResourceTransaction.resume(XAResourceTransaction.java:297)

The hexdump implementation is creating an XA statement as followed:

XA PREPARE 0x 31 39 32 2E 31 36 38 2E 32 35 31 2E 32 2E 74 6D 192.168.251.2.tm
31 34 39 36 36 30 31 31 37 38 38 32 35 30 32 35 1496601178825025
34 31 41
,0x
31 39 32 2E 31 36 38 2E 32 35 31 2E 32 2E 74 6D 192.168.251.2.tm
32 30 34 37 2047
,1096044365

This leads to an exception.

The provided implementation is corresponding to the mysql implementation or atomikos implementation.
The result would be:

XA PREPARE 0x3139322E3136382E3235312E322E746D313439363630313137383832353032353431,0x3139322E3136382E3235312E322E746D32303437,1096044365

@rusher rusher merged commit abe6ecf into mariadb-corporation:master Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants