You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Pushkar Raste (JIRA)" <ji...@apache.org> on 2017/01/06 19:45:58 UTC

[jira] [Updated] (ZOOKEEPER-2659) Use log4j2 as a logging framework as log4j 1.X is now deprecated

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

Pushkar Raste updated ZOOKEEPER-2659:
-------------------------------------
    Attachment: zk_log4j2_migration.patch

Here is initial patch. I still need to clean it up, but want to get conversation started. 

Zookeeper currently registers all the loggers with JMX. I don't think {{log4j2}} provides a way to register arbitrary loggers with JMX. However for {{log4j2}} JMX is enabled by default https://logging.apache.org/log4j/2.0/manual/jmx.html



> Use log4j2 as a logging framework as log4j 1.X is now deprecated
> ----------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2659
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2659
>             Project: ZooKeeper
>          Issue Type: Wish
>            Reporter: Pushkar Raste
>            Priority: Minor
>         Attachments: zk_log4j2_migration.patch
>
>
> Zookeeper currently uses {{log4j 1.X}} as the default logging framework. {{log4j 1.X}} is now deprecated http://logging.apache.org/log4j/1.2/
> This ticket is to track efforts to move zookeeper to {{log4j2}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)