[
https://issues.apache.org/jira/browse/OOZIE-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16643098#comment-16643098
]
Peter Bacsko commented on OOZIE-3136:
-------------------------------------
Regarding the bridge, check this out:
https://logging.apache.org/log4j/log4j-2.2/log4j-1.2-api/index.html
"To use the Log4j Legacy Bridge just remove all the Log4j 1.x jars from the
application and replace them with the bridge jar. Once in place all logging
that uses Log4j 1.x will be routed to Log4j 2. *However, applications that
attempt to modify legacy Log4j by adding Appenders, Filters, etc may experience
problems if they try to verify the success of these actions as these methods
are largely no-ops*."
Do we do anything like that? I mean, messing around log4j classes directly.
This must be checked.
If we directly use stuff like {{PropertyConfigurator}}, that's a no-op in the
bridge. We must also make sure that initial {{Logger.getlogger()}} calls
configure the Log4j2 based on the original log4j properties file. I just
checked this and does not seem to be the case - there is a converter class, but
looks like we have to call that manually.
So there are quite a few things to consider/validate here.
> Upgrade from Log4j 1.x to 2.x
> -----------------------------
>
> Key: OOZIE-3136
> URL: https://issues.apache.org/jira/browse/OOZIE-3136
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Attila Sasvari
> Assignee: Julia Kinga Marton
> Priority: Major
>
> {{5 August 2015 --The Apache Logging Services™ Project Management Committee
> (PMC) has announced that the Log4j™ 1.x logging framework has reached its end
> of life (EOL) and is no longer officially supported.}}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> We should upgrade from Log4j 1.x to 2.x . Perhaps we could use slf4j .
> Related tickets: MAPREDUCE-6983, HADOOP-12956, OOZIE-3135
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
