[
https://issues.apache.org/jira/browse/KNOX-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630372#comment-16630372
]
Kevin Risden edited comment on KNOX-1462 at 10/4/18 7:50 PM:
-------------------------------------------------------------
I started a bit on this. Rough so far so just in a branch.
https://github.com/apache/knox/pull/32
I was able to:
* Removed/excluded log4j 1.x dependencies
* update appenders to work with Log4j2
* Migrate from MDC to ThreadContext
* Migrate some of the log4j.properties to log4j2.xml files
* Check that tests are passing for logging on JDK 8
I need to go back and clean it up but promising.
was (Author: risdenk):
I started a bit on this. Rough so far so just in a branch.
[https://github.com/risdenk/knox/commits/KNOX-1462]
I was able to:
* Removed/excluded log4j 1.x dependencies
* update appenders to work with Log4j2
* Migrate from MDC to ThreadContext
* Migrate some of the log4j.properties to log4j2.xml files
* Check that tests are passing for logging on JDK 8
I need to go back and clean it up but promising.
> Migrate from Log4j 1.x to 2.x
> -----------------------------
>
> Key: KNOX-1462
> URL: https://issues.apache.org/jira/browse/KNOX-1462
> Project: Apache Knox
> Issue Type: Improvement
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Blocker
> Fix For: 1.2.0
>
>
> Assigning to version 1.2.0 to have a discussion about it.
> Log4j 1.x went EOL in August 2015. JDK 9+ support (KNOX-1458) will require
> Log4j 2 since Knox uses MDC for all the audit logging. More details about the
> issue and migration are found here:
> * [https://blogs.apache.org/logging/entry/moving_on_to_log4j_2]
> * [https://logging.apache.org/log4j/2.x/manual/migration.html]
> Items of "concern"
> * MDC migrate to ThreadContext
> * log4j.properties need to migrate to log4j2.xml (or yaml or json)
> Benefits
> * Async logging
> * Dynamic reloading of configuration changes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
