Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <861187664.1218493964707.JavaMail.jira@brutus>
Date: Mon, 11 Aug 2008 15:32:44 -0700 (PDT)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3934) Update log4j from 1.2.13 to 1.2.15
In-Reply-To: <355224519.1218484246218.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer updated HADOOP-3934:
-------------------------------------

    Priority: Blocker  (was: Major)

> 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
>            Reporter: Don Kim
>            Priority: Blocker
>
> 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.