WFLY-21390 Fix memory leak of ComponentConfiguration after deployment being retained due to lambdas#19551
Merged
bstansberry merged 1 commit intowildfly:mainfrom Jan 27, 2026
Merged
Conversation
jamezp
previously approved these changes
Jan 26, 2026
bstansberry
previously approved these changes
Jan 26, 2026
…nt being retained due to lambdas ComponentConfiguration objects were being retained after deployment due to lambda expressions capturing entire configuration objects when they only needed specific values. Since these lambdas were stored in long-lived MSC services (e.g., BinderService), the deployment-time configuration remained in memory indefinitely. Fix lambda captures in ViewDescription and EjbJndiBindingsDeploymentUnitProcessor Refactor StatefulSessionBeanCacheProvider SPI to avoid retaining configuration. Signed-off-by: Radoslav Husar <radosoft@gmail.com>
Discovered more issues and significantly refactored; needs re-review.
bstansberry
approved these changes
Jan 27, 2026
jamezp
approved these changes
Jan 27, 2026
Contributor
Member
Author
|
Thats correct. I will handle the rest in the morning. |
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
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.
ComponentConfiguration objects were being retained after deployment due to lambda expressions capturing entire configuration objects when they only needed specific values.
Since these lambdas were stored in long-lived MSC services (e.g., BinderService), the deployment-time configuration remained in memory indefinitely.
Fix lambda captures in ViewDescription and EjbJndiBindingsDeploymentUnitProcessor
Refactor StatefulSessionBeanCacheProvider SPI to avoid retaining configuration.
Resolves
https://issues.redhat.com/browse/WFLY-21390