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

Error enlisting after update to 3.1.0 in MariaDB and DB2 #140

Closed
oburgosm opened this issue Apr 19, 2024 · 2 comments · Fixed by #141
Closed

Error enlisting after update to 3.1.0 in MariaDB and DB2 #140

oburgosm opened this issue Apr 19, 2024 · 2 comments · Fixed by #141

Comments

@oburgosm
Copy link

I have an application that use narayana-spring-boot with JPA and works fine with 3.0.0. After update it to 3.1.0 it begin to fail with MariaDB and DB2, although it runs with Postgres or H2.

I have been investigating the error and looks like the problem is on commit bbadc28.

My application has the following property:

narayana.transaction-manager-id=${random.uuid}

Then, like transaction-manager-id has more than 28 bytes, it's replaced with value generated with the new function shortenNodeIdentifier. But this cause that MariaDB and DB2 fail starting transaction (enlisting it). In case of MariaDB it throws a SQLSysntaxException.

@graben
Copy link
Contributor

graben commented Apr 29, 2024

@oburgosm: I think this issue can be closed

@oburgosm
Copy link
Author

oburgosm commented May 6, 2024

Yes, It's solved in 3.1.1 via #141. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants