You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/26 15:48:00 UTC

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

     [ https://issues.apache.org/jira/browse/KNOX-1462?focusedWorklogId=204560&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-204560 ]

ASF GitHub Bot logged work on KNOX-1462:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Feb/19 15:47
            Start Date: 26/Feb/19 15:47
    Worklog Time Spent: 10m 
      Work Description: risdenk commented on pull request #32: KNOX-1462 - Migrate from Log4j 1.x to 2.x
URL: https://github.com/apache/knox/pull/32
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 204560)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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: 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
(v7.6.3#76005)