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

Fix race condition during the update of multiple entites #1687

Closed
DavideD opened this issue Jun 29, 2023 · 0 comments · Fixed by #1690
Closed

Fix race condition during the update of multiple entites #1687

DavideD opened this issue Jun 29, 2023 · 0 comments · Fixed by #1690
Labels
bug Something isn't working
Milestone

Comments

@DavideD
Copy link
Member

DavideD commented Jun 29, 2023

Under load, the CompletionStage responsible for signaling a successful update operation might not complete. This causes the user's application to block without apparent reason.

The bug is in ReactiveUpdateStandardCoordinator.

@DavideD DavideD added the bug Something isn't working label Jun 29, 2023
@DavideD DavideD added this to the next milestone Jun 29, 2023
@DavideD DavideD linked a pull request Jun 29, 2023 that will close this issue
DavideD added a commit to DavideD/hibernate-reactive that referenced this issue Jun 30, 2023
Hibernate ORM can use the same update coordinator among
multiple update operations.

In Hibernate Reactive, the reactive update coordinator
has a state that cannot be shared. So, we decided
to create a new scoped coordinator for each update
operation.

Right now, we want to merge a fix for the issue that
doesn't require us to copy or change code from
Hibernate ORM.

The plan is to find a more efficient solution as
a separate issue. And, possible add some
infrastructure to make it easier to track these
type of issues.
DavideD added a commit to DavideD/hibernate-reactive that referenced this issue Jun 30, 2023
Hibernate ORM can use the same update coordinator among
multiple update operations.

In Hibernate Reactive, the reactive update coordinator
has a state that cannot be shared. So, we decided
to create a new scoped coordinator for each update
operation.

Right now, we want to merge a fix for the issue that
doesn't require us to copy or change code from
Hibernate ORM.

The plan is to find a more efficient solution as
a separate issue. And, possible add some
infrastructure to make it easier to track these
type of issues.
DavideD added a commit to DavideD/hibernate-reactive that referenced this issue Jun 30, 2023
Hibernate ORM can use the same update coordinator among
multiple update operations.

In Hibernate Reactive, the reactive update coordinator
has a state that cannot be shared. So, we decided
to create a new scoped coordinator for each update
operation.

Right now, we want to merge a fix for the issue that
doesn't require us to copy or change code from
Hibernate ORM.

The plan is to find a more efficient solution as
a separate issue. And, possible add some
infrastructure to make it easier to track these
type of issues.
DavideD added a commit to DavideD/hibernate-reactive that referenced this issue Jun 30, 2023
Hibernate ORM can use the same update coordinator among
multiple update operations.

In Hibernate Reactive, the reactive update coordinator
has a state that cannot be shared. So, we decided
to create a new scoped coordinator for each update
operation.

Right now, we want to merge a fix for the issue that
doesn't require us to copy or change code from
Hibernate ORM.

The plan is to find a more efficient solution as
a separate issue. And, possible add some
infrastructure to make it easier to track these
type of issues.
Sanne pushed a commit that referenced this issue Jun 30, 2023
Hibernate ORM can use the same update coordinator among
multiple update operations.

In Hibernate Reactive, the reactive update coordinator
has a state that cannot be shared. So, we decided
to create a new scoped coordinator for each update
operation.

Right now, we want to merge a fix for the issue that
doesn't require us to copy or change code from
Hibernate ORM.

The plan is to find a more efficient solution as
a separate issue. And, possible add some
infrastructure to make it easier to track these
type of issues.
@DavideD DavideD modified the milestones: next, 2.0.2.Final Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant