Upgrade to latest JGroups patch version to resolve thread pinning #37286
Conversation
This file contains hidden or 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
Closes keycloak#37285 Signed-off-by: Alexander Schwartz <[email protected]>
Contributor
Author
|
@pruivo - please review when you have the time. I might be tempted to backport it to KC 26.1. |
Contributor
Author
|
@mhajas - can you please approve and merge based on Pedro's review? Thanks! |
2 tasks
Contributor
Author
I placed this very close to the ISPN version number in the POM, so I would hope that this isn't needed. |
ahus1
added a commit
to ahus1/keycloak
that referenced
this pull request
Feb 12, 2025
…ycloak#37286) Closes keycloak#37285 Signed-off-by: Alexander Schwartz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Closes #37285
My local test didn't show pinned threads with the pure JGroups communication. Just org.infinispan.topology.ClusterCacheStatus seems to have one pinned placed when a node leaves.
It seems that the ISPN 15.0.x branch was already updated in infinispan/infinispan#14021 so it should arrive soon with a regular ISPN release.