-
Notifications
You must be signed in to change notification settings - Fork 170
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
log4j v2 update #1970
log4j v2 update #1970
Conversation
I've made my best attempt to migrate log4j.xml to the new log4j v2 format. As part of these changes, we can/should remove the |
Also worth noting: I've done my best to preserve backwards compatibility while also incorporating the changes that were recently introduced in #1913. |
In comparing the logs from an instance of WebAPI v2.10.1 vs an instance running this branch I have two observations:
<audit.trail.enabled>true</audit.trail.enabled>
<audit.trail.log.file>D:/apache-tomcat-8.5.63/logs/audit/audit.log</audit.trail.log.file>
<audit.trail.log.extraFile>D:/apache-tomcat-8.5.63/logs/audit/audit-extra.log</audit.trail.log.extraFile>
My guess is that there may be duplicate loggers registered in the code base. This feels fairly minor but noting it for completeness. |
pom.xml
Outdated
@@ -13,7 +13,7 @@ | |||
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> | |||
<!-- Spring Boot manages spring.version as well --> | |||
<spring.boot.version>1.5.22.RELEASE</spring.boot.version> | |||
<log4j2.version>2.15.0</log4j2.version> | |||
<log4j2.version>2.16.0</log4j2.version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should use 2.17.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed - as a matter of fact, we should probably keep this branch open until the release cycle slows a bit. There have been 3 releases in the past 3 weeks alone: https://logging.apache.org/log4j/2.x/changes-report.html.
Ok, for the sake of expediting this fix, let's settle on a confirm fix for the reported vulnerability, and get it into master, and then cherry pick it for a hotfix into our maintenance branch. Sound good? |
@chrisknoll I had to make it properly via a merge to the 'master' and then cherry-picking to the 'master-2.10'. You are right. In the same time Anthony mentioned this branch is going to be open for some time. I merged parts which belong to log4j (didn't include removing of no longer used profiels) right away into 'master-2.10'. There was an intention to release 2.10.2 in the nearest days which include log4j 1.x -> 2.x migration Known issues:
|
Is this going to use 2.17.1? I'm seeing that this is needed now, as 2.17.0 has yet another vulnerability. Never mind -- I see it now |
We'll keep this PR open until the release cycle from Apache log4j slows a bit. |
* Update log4j2.xml configuration * Bump to log4j v2.17.1
Aims to address #1969 by updating log4j to V2.15.0. This is a draft of a PR since it requires additional work to migrate log4j.xml to use the new format. I've included
src/main/resources/log4j2.xml
as part of this PR to give us a starting point.