[fix](jni) fix JNI logging by migrating to log4j2 with proper configuration#60584
Open
morningman wants to merge 4 commits intoapache:masterfrom
Open
[fix](jni) fix JNI logging by migrating to log4j2 with proper configuration#60584morningman wants to merge 4 commits intoapache:masterfrom
morningman wants to merge 4 commits intoapache:masterfrom
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 30491 ms |
ClickBench: Total hot run time: 28.14 s |
Contributor
FE UT Coverage ReportIncrement line coverage `` 🎉 |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
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.
The BE's jni.log was not being written to because the JNI scanner module
was using log4j 1.x APIs which were not properly configured in the JNI
classloader environment.
Changes:
logging works in JNI environment
plugin loading
via ExceptionUtils.getRootCauseMessage()