-
Notifications
You must be signed in to change notification settings - Fork 96
Need to abort/rollback transactions on error #1514
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
Comments
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
We need to test with Mutiny and with CompletionStage because the exception is thrown by the API classes. I've also cleaned up a bit the code to avoid NullPointerException in case of failures (it should throw the correct assertion error).
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
Before, we were ignoring some errors if they were happening in the worker provided to the transactions. Because of this, the transaction wasn't always rollbacked or closed.
DavideD
pushed a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
…ctions" This reverts commit 4a997c5.
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
We need to test with Mutiny and with CompletionStage because the exception is thrown by the API classes. I've also cleaned up a bit the code to avoid NullPointerException in case of failures (it should throw the correct assertion error).
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
Before, we were ignoring some errors if they were happening in the worker provided to the transactions. Because of this, the transaction wasn't always rollbacked or closed.
DavideD
pushed a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
We need to test with Mutiny and with CompletionStage because the exception is thrown by the API classes. I've also cleaned up a bit the code to avoid NullPointerException in case of failures (it should throw the correct assertion error).
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
Before, we were ignoring some errors if they were happening in the worker provided to the transactions. Because of this, the transaction wasn't always rollbacked or closed.
DavideD
pushed a commit
to DavideD/hibernate-reactive
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
that referenced
this issue
Feb 17, 2025
We need to test with Mutiny and with CompletionStage because the exception is thrown by the API classes. I've also cleaned up a bit the code to avoid NullPointerException in case of failures (it should throw the correct assertion error).
DavideD
added a commit
that referenced
this issue
Feb 17, 2025
DavideD
added a commit
that referenced
this issue
Feb 17, 2025
Before, we were ignoring some errors if they were happening in the worker provided to the transactions. Because of this, the transaction wasn't always rollbacked or closed.
DavideD
pushed a commit
that referenced
this issue
Feb 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would seem that if I introduce assertions to check that the current transaction is terminated (in any way) before we close the connection, there's at least one test failing:
"ReactiveStatelessProxyUpdateTest. testLazyInitializationException"
We need to investigate this to ensure such resources don't leak under any circumstances.
Providing a test as a PR soon
The text was updated successfully, but these errors were encountered: