Skip to content
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

LOG4J2-3358: Fix substitutions when programmatic configuration is used #726

Merged
merged 1 commit into from Jan 22, 2022

Conversation

carterkozak
Copy link
Contributor

@carterkozak carterkozak commented Jan 21, 2022

The problem is that some configuration creation paths fail to
use the Interpolator constructor which loads all plugins. This
produces inconsistent behavior based on the configuration construction
path.
By merging code-paths, we can provide consistent behavior.

@carterkozak
Copy link
Contributor Author

carterkozak commented Jan 21, 2022

in 2.17.1 we paired down the list of allowed lookups based on javadoc, however that wasn't correct because the objects aren't always used precisely how the AbstractConfiguration expects, leading to vastly different behavior based on how the configuration (thus StrSubstitutor) is created.

The problem is that some configuration creation paths fail to
use the Interpolator constructor which loads all plugins. This
produces inconsistent behavior based on the configuration construction
path.
By merging code-paths, we can provide consistent behavior.
@carterkozak carterkozak changed the title LOG4J2-3358: Fix substitutions when the DefaultConfiguraiton is used LOG4J2-3358: Fix substitutions when programmatic configuration is used Jan 21, 2022
@carterkozak carterkozak merged commit 7ca3c4f into apache:release-2.x Jan 22, 2022
carterkozak added a commit that referenced this pull request Jan 22, 2022
#726)

The problem is that some configuration creation paths fail to
use the Interpolator constructor which loads all plugins. This
produces inconsistent behavior based on the configuration construction
path.
By merging code-paths, we can provide consistent behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants