You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2019/11/09 15:14:00 UTC

[jira] [Assigned] (KNOX-1462) Migrate from Log4j 1.x to 2.x

     [ https://issues.apache.org/jira/browse/KNOX-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Risden reassigned KNOX-1462:
----------------------------------

    Assignee:     (was: Kevin Risden)

> 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
>            Priority: Blocker
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)