hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-6807) Log directly from jetty to commons logging, bypassing SLF4J
Date Thu, 03 Jun 2010 13:47:59 GMT
Log directly from jetty to commons logging, bypassing SLF4J
-----------------------------------------------------------

                 Key: HADOOP-6807
                 URL: https://issues.apache.org/jira/browse/HADOOP-6807
             Project: Hadoop Common
          Issue Type: Improvement
          Components: io
    Affects Versions: 0.21.0
            Reporter: Steve Loughran
            Priority: Minor


Jetty may default to logging through SLF4J, but don't actually need it; you can provide your
own logger which goes straight to commons-logging, I've done something similar in the past:

[[http://smartfrog.svn.sourceforge.net/viewvc/smartfrog/trunk/core/components/jetty/src/org/smartfrog/services/jetty/log/]]

You just need to point jetty at the relevant logger by setting up the relevant JVM property,
such as {{-Dorg.mortbay.log.class=org.smartfrog.services.jetty.log.JettyLogger}}. Doing something
similar in Avro/Hadoop-common would eliminate SLF4J from the dependency graph, route via commons-logging
and then, usually, to Log4J, so having only one log to manage. All JVM startup scripts would
need to set the relevant property, it is harmless on JVMs that don't start up Jetty6+

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message