[
https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623348#action_12623348
]
Steve Loughran commented on HADOOP-3934:
----------------------------------------
> Hadoop is built with a non-standard version of Log4J
I don't see that
hadoop-core> md5sum lib/log4j-1.2.13.jar
52169b4a318e3246483f39f62b84b948 lib/log4j-1.2.13.jar
~/.ivy2/cache/log4j/log4j/jars> md5sum log4j-1.2.13.jar
52169b4a318e3246483f39f62b84b948 log4j-1.2.13.jar
Looks like a standard release to me, or at least to md5sum.
> Update log4j from 1.2.13 to 1.2.15
> ----------------------------------
>
> Key: HADOOP-3934
> URL: https://issues.apache.org/jira/browse/HADOOP-3934
> Project: Hadoop Core
> Issue Type: Improvement
> Affects Versions: 0.18.0
> Reporter: Don Kim
> Priority: Blocker
> Fix For: 0.18.1
>
>
> Hadoop is currently using log4j version 1.2.13 and this version does not
> support the use of a non-default syslog port when specifying the syslog
> server destination. Syslogging is important to us and even more so with
> audit logging introduced in hadoop-0.18. The current released version of
> log4j is 1.2.15 which does support the use of specifying a non-default syslog
> port (introduced in log4j 1.2.14) as well as many other syslog enhancements
> and fixes (http://logging.apache.org/log4j/1.2/changes-report.html).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
