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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2014/01/25 20:52:37 UTC

[jira] [Created] (HADOOP-10288) Explicit reference to Log4JLogger breaks non-log4j users

Todd Lipcon created HADOOP-10288:
------------------------------------

             Summary: Explicit reference to Log4JLogger breaks non-log4j users
                 Key: HADOOP-10288
                 URL: https://issues.apache.org/jira/browse/HADOOP-10288
             Project: Hadoop Common
          Issue Type: Bug
          Components: util
    Affects Versions: 2.4.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


In HttpRequestLog, we make an explicit reference to the Log4JLogger class for an instanceof check. If the log4j implementation isn't actually on the classpath, the instanceof check throws NoClassDefFoundError instead of returning false. This means that dependent projects that don't use log4j can no longer embed HttpServer -- typically this is an issue when they use MiniDFSCluster as part of their testing.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)