avoid loading application log4j plugins#1214
Merged
SylvainJuge merged 2 commits intoelastic:masterfrom Jun 5, 2020
Merged
Conversation
felixbarny
approved these changes
Jun 3, 2020
Codecov Report
@@ Coverage Diff @@
## master #1214 +/- ##
============================================
+ Coverage 59.24% 59.90% +0.65%
- Complexity 87 94 +7
============================================
Files 339 344 +5
Lines 16026 16680 +654
Branches 2248 2384 +136
============================================
+ Hits 9495 9992 +497
- Misses 5881 6006 +125
- Partials 650 682 +32
Continue to review full report at Codecov.
|
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
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.
Found while testing with an application that is using log4j2.
Shaded log4j2 from agent tries to load application plugins, this is due to having hard-coded references to
Log4j2Plugins.datwithinMETA-INFfolder (which is not covered by relocation patterns)Classes that trigger this issue can be found using the following one-liner command within an expanded copy of the agent jar.
We only have two of them