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
ISPN-12725 Conflict resolution fails in transactional cache with auto-commit disabled #9051
ISPN-12725 Conflict resolution fails in transactional cache with auto-commit disabled #9051
Conversation
@pruivo updated to include the IllegalArgumentException fix |
caee5c5
to
9ab1f92
Compare
Updated to fix the test failures (sometimes the transaction manager is null) and to rebase on master. |
* | ||
* @author Ryan Emerson | ||
* @since 9.1 | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs updating or removed 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danberindei Other than the javadoc, LGTM!
* Log only one message, at error level * Fix other ComponentRef.getName() references
The entry returned by AdvancedCache.getCacheEntry(key) is not always an InternalCacheEntry.
9ab1f92
to
b250163
Compare
Thanks @danberindei |
https://issues.redhat.com/browse/ISPN-12725
https://issues.redhat.com/browse/ISPN-12715
https://issues.redhat.com/browse/ISPN-12717
ISPN-12725 Conflict resolution fails in transactional cache with auto-commit disabled
ISPN-12715 Conflict resolution failure logged at debug level
ISPN-12717 DefaultConflictManager.getAllVersions fails in tx caches