WFLY-3731 StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back #6601
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er a Synchronization if the transaction was rolled back
|
Build 4523 is now running using a merge of 86a5dca |
|
Build 4523 outcome was SUCCESS using a merge of 86a5dca |
stuartwdouglas
added a commit
that referenced
this pull request
Aug 17, 2014
…nchronizationInterceptor WFLY-3731 StatefulSessionSynchronizationInterceptor should not register a Synchronization if the transaction was rolled back
scottmarlow
deleted the
WFLY-3731_StatefulSessionSynchronizationInterceptor
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Doing so will cause an ISE "IllegalStateException: No transaction is running" to be thrown when registering the Synchronization (see http://fpaste.org/125252 for call stack).