You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/09/09 22:37:44 UTC
[jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
[ https://issues.apache.org/jira/browse/HADOOP-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-3934:
----------------------------------
Fix Version/s: (was: 0.19.0)
0.18.1
This was needed for 0.18 deployment. I also included the fix from HADOOP-4037.
> 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
> Assignee: Owen O'Malley
> 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.