[2.7] CacheKey NPE and DeadLock issue #2147
Draft
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
Signed-off-by: Radek Felcman <[email protected]>
rfelcman
changed the title
rfelcman
force-pushed
the
dead_lock_cache_key_npe_2.7
branch
from
4ce1c16
to
ca87082
Compare
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.
This is initial POC/fix for #2114 #2100 and #2094
I think, that changes will be there. This PR is mentioned as start point of the discussion as deadlock are is complex and complicated to simulate.
It's based on latest 2.7 version where are in some code parts instead if
synchronizedjava.util.concurrent.locks.Lockandjava.util.concurrent.locks.ReentrantLockdue a JDK Loom (Virtual Threads) performance.