-
Notifications
You must be signed in to change notification settings - Fork 92
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
Reactive find with lock in Quarkus with reactive hibernate - Issue reproduced #1905
Comments
Thanks for the project. I can see the error. It seems quite complicated to solve, but I will give it a try |
Hi @alexjaravete , I tried to run your reproducer and all tests pass |
@dreab8, do you mean that this work in Hibernate Reactive 3? |
@DavideD I tried with the reproducer provided by @alexjaravete that uses 2.2.2 and the tests pass |
Added
and the problem showed up. Thanks @DavideD |
… reactive hibernate
… reactive hibernate
… reactive hibernate
… reactive hibernate
… reactive hibernate
… reactive hibernate
… reactive hibernate
Hi, this is related to this issue #1896.
I was able to reproduce the issue when using a
OneToMany
andManyToOne
relationship.By doing this, hibernate is forced to do a
JOIN
and theSELECT FOR UDPATE
cannot be done in the same request.When hibernate is trying to do the followup Lock, it throws an error.
The error should already show up after creating a
Fruit
and fetching it.No
Owner
object is needed.It's only there to trigger the issue.
This is the repository with the reproduced issue: https://github.com/alexjaravete/quarkus-quickstarts/tree/findById/hibernate-reactive-panache-quickstart
The text was updated successfully, but these errors were encountered: