May 2007 - logback-user - mailman3.qos.ch

Changing a logger's level for only one appender?
by Gerweck Andy - agerwe 21 May '07

21 May '07

Hello, I have a couple of applications that create two log files: one with all debug statements for troubleshooting and another with just INFO and above for general information. The debug logs are erased after a day or two while the general log is kept for a month or longer. I apologize if I just missed this in the documentation, but is there an easy way to set the minimum level for a specific logger hierarchy on just a single appender. For example, I want com.example.* to write only WARN and above to my general log, but I still want its DEBUG statements in the debug log. I'm sure I could write my own filter or use an EvaluatorFilter, but this seems like such a common requirement that there would be a standard mechanism. Thanks, Andy *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ****************************************************************************

2 3

logback performace going down
by Mandeep Singh 21 May '07

21 May '07

Hi, I had downloaded the logback version 0.9.2 sometime back and had done some performance comparison vis a vis log4j. At that time the tested call (logger.isDebugEnabled) was atleast 3 times faster in logback then log4j. But just today i downloaded the 0.9.5 version and it seems that due to some changes the performance has been hit . Now logback is a bit slower then log4j for the same call . (Although i must add that the performance of parameterized call has improved, and it now takes half of the time as compared to 0.9.2) I am pasting the code used for the test. - Mandeep ==================================================================================================== ==================================================================================================== package mandy.test.programs; import org.slf4j.Logger; import org.slf4j.LoggerFactory; public class LogTester2 { static Logger logbacklogger = LoggerFactory.getLogger(LogTester2.class); static org.apache.log4j.Logger log4jlogger = org.apache.log4j.Logger.getLogger(LogTester2.class); // How many times should we try to log: static int loop = 1000000; public static void main(String[] args) throws InterruptedException { initConfig(); // Let's run once for Just In Time compiler log4jDirectDebugCall(); log4jTestedDebugCall(); logbackDirectDebugCall(); logbackTestedDebugCall(); logbackParametrizedDebugCall(); // let's run the tests and display the results: long result1 = log4jDirectDebugCall(); long result2 = log4jTestedDebugCall(); long result3 = logbackDirectDebugCall(); long result4 = logbackTestedDebugCall(); long result5 = logbackParametrizedDebugCall(); System.out.println("###############################################"); System.out.println("Log4j direct debug call: " + result1); System.out.println("Log4j tested (isDebugEnabled) debug call: " + result2); System.out.println("Logback direct debug call: " + result3); System.out.println("Logback tested (isDebugEnabled) debug call: " + result4); System.out.println("Logback parametrized debug call: " + result5); System.out.println("###############################################"); } private static long log4jDirectDebugCall() { Integer j = new Integer(2); long start = System.nanoTime(); for (int i = 0; i < loop; i++ ) { log4jlogger.debug("SEE IF THIS IS LOGGED " + j + "."); } return (System.nanoTime() - start) / loop; } private static long log4jTestedDebugCall() { Integer j = new Integer(2); long start = System.nanoTime(); for (int i = 0; i < loop; i++ ) { if (log4jlogger.isDebugEnabled()) { log4jlogger.debug("SEE IF THIS IS LOGGED " + j + "."); } } return (System.nanoTime() - start) / loop; } private static long logbackDirectDebugCall() { Integer j = new Integer(2); long start = System.nanoTime(); for (int i = 0; i < loop; i++ ) { logbacklogger.debug("SEE IF THIS IS LOGGED " + j + "."); } return (System.nanoTime() - start) / loop; } private static long logbackTestedDebugCall() { Integer j = new Integer(2); long start = System.nanoTime(); for (int i = 0; i < loop; i++ ) { if (logbacklogger.isDebugEnabled()) logbacklogger.debug("SEE IF THIS IS LOGGED " + j + "."); } return (System.nanoTime() - start) / loop; } private static long logbackParametrizedDebugCall() { Integer j = new Integer(2); long start = System.nanoTime(); for (int i = 0; i < loop; i++ ) { logbacklogger.debug("SEE IF THIS IS LOGGED {}.", j); } return (System.nanoTime() - start) / loop; } private static void initConfig() { org.apache.log4j.Logger log4jRoot = org.apache.log4j.Logger.getRootLogger(); log4jRoot.setLevel(org.apache.log4j.Level.INFO); ch.qos.logback.classic.Logger lbRoot = (ch.qos.logback.classic.Logger) LoggerFactory.getLogger("ROOT"); lbRoot.setLevel(ch.qos.logback.classic.Level.INFO); // create the loggers org.apache.log4j.Logger.getLogger("perfTest"); org.apache.log4j.Logger.getLogger("perfTest.ch"); org.apache.log4j.Logger.getLogger("perfTest.ch.qos"); org.apache.log4j.Logger.getLogger("perfTest.ch.qos.logback"); LoggerFactory.getLogger("perfTest"); LoggerFactory.getLogger("perfTest.ch"); LoggerFactory.getLogger("perfTest.ch.qos"); LoggerFactory.getLogger("perfTest.ch.qos.logback"); } } ____________________________________________________________________________________Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/

1 0

Question regarding jmxConfigurator
by Klaus UNGER 09 May '07

09 May '07

Hello, maybe a "stupid" question, but is there anywhere an example or explanation who to use jmx configuration capabilities without a web-server (tomcat/jetty) I do have a RCP rich client, have already successfully implemented a draft ILogAppender. Now we wanted to be able to dynamically configure Log-Levels via JMX I didn't find a port to connect to the client on my local machine! thanks in advance K:) --------------------- Klaus UNGER, BSc Münzgasse 3/40+42 A-1030 Wien mobil: +43 (664) 4236046

2 1

Unable to Initialize Logger in JDK1.4
by Brian Suksomwong 03 May '07

03 May '07

Hey all, I'm trying to test logback's JDK1.4 support, but am receiving a NoClassDefNotFoundException when running my test class. Test Class: import org.slf4j.Logger; import org.slf4j.LoggerFactory; public Test { public static void main(String args[]) { Logger log = LoggerFactory.getLogger(Test.class); System.out.prinln(log.getName()); } } My classpath includes: logback-classic-0.9.5-jdk14.jar logback-core-0.9.5-jdk14.jar slf4j-api-1.3.0.jar slf4j-jdk14-1.3.0.jar (just in case, but I receive the same error without it) When I try to run the class I receive the following stack trace: java.lang.NoClassDefFoundError: javax/management/ObjectName at ch.qos.logback.classic.joran.JoranConfigurator.addInstanceRules( JoranConfigurator.java:62) at ch.qos.logback.core.joran.GenericConfigurator.buildInterpreter( GenericConfigurator.java:83) at ch.qos.logback.core.joran.JoranConfiguratorBase.buildInterpreter( JoranConfiguratorBase.java:82) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:95) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:74) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:38) at ch.qos.logback.classic.util.ContextInitializer.configureByResource( ContextInitializer.java:24) at ch.qos.logback.classic.util.ContextInitializer.autoConfig( ContextInitializer.java:35) at ch.qos.logback.classic.util.ContextInitializer.autoConfig( ContextInitializer.java:46) at org.slf4j.impl.StaticLoggerBinder.initialize(StaticLoggerBinder.java:52) at org.slf4j.impl.StaticLoggerBinder.<init>(StaticLoggerBinder.java:44) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:39) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:57) at Test.main(Test.java:6) ... Removed 21 stack frames The javax/management package is not in JDK1.4, but is in JDK1.5. I think there is a binding issue happening; please help me solve this issue if possible. Thanks! -B-

3 3

wizard to create logback.xml
by dirk ooms 03 May '07

03 May '07

Hello list, i created a wizard that generates a logback.xml for logging to file, console, socket and/or email: http://wizardforge.org/pc?action=showVersion&id=72 enjoy, dirk

2 2

Dynamic (per Marker ?) file appender
by franck.routier＠axege.com 03 May '07

03 May '07

Hi, Would it be feasable to have a file appender that would log to a file dynamically created based on a Marker ? The use case I have in mind is I "launch jobs", and would like each job to have its own logging file (identified by an incremental job number for example). Would the use of marker to do so be feasable, be a good idea, imply to create a new appender class, be totally dumb :), ...? Thanks for your comments, Franck

2 1

logback and concurrency
by Xavier Hanin 03 May '07

03 May '07

Hi Logback community, I've read somewhere that logback is thread safe, but I would like some confirmation about that and what does it imply. So, first, is logback Logger implementation thread safe? Second, what is the recommended pattern to get a logger and use it: - create and store it in a static variable - create and store it in an instance variable - create and store it in a local variable Thanks in advance, Xavier -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/

2 1

Changing appenders at runtime
by Richard Wallace 03 May '07

03 May '07

Hello, I'm trying to change the appender used at runtime during testing. I'm using the excellent Unitils project to do my unit testing and am unit testing some Hibernate and Spring stuff. The amount that gets logged is too much to do to stdout so I want it to go to a file. My problem is that if I just do it to a single file all the logs run together and you have a hard time telling where one test begins and another ends. So I want to change the file that is being logged to for each test. I've got the following bit of code that runs before each test class. LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory (); Logger logger = lc.getLogger (LoggerContext.ROOT_NAME); m_originalAppender = (FileAppender) logger.detachAppender ("FILE"); String logFile = System.getProperty ("test.log.dir") + File.separator + testClass.getName () + ".log"; FileAppender classAppender = new FileAppender (); classAppender.setContext (lc); classAppender.setName ("FILE"); classAppender.setFile (logFile); classAppender.setAppend (false); classAppender.setLayout (m_originalAppender.getLayout ()); classAppender.setEncoding (m_originalAppender.getEncoding ()); classAppender.start (); and here is the initial logback.xml configuration. <configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <File>test.log</File> <Append>true</Append> <Encoding>UTF-8</Encoding> <BufferedIO>false</BufferedIO> <ImmediateFlush>true</ImmediateFlush> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern> %-4relative [%thread] %-5level %logger{36} - %msg%n </pattern> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE" /> </root> </configuration> Logging starts going to the test.log file successfully and then the testClass log file gets created, but nothing is logged to it. I'm sure I'm missing something about correctly attaching it or having it listen for logging events, but I can't figure out where. Any hints? Thanks, Rich

2 1

SimpleSocketServer as Daemon
by Stefan Armbruster 03 May '07

03 May '07

Hi, Jakarta Commons Daemon (http://jakarta.apache.org/commons/daemon) provides support for running "normal" java classes like unix/windows system daemons/services. The class to be deamonized must either implement the Daemon interface or simply implement a few public methods (init, start, stop, destroy). When using the latter, no additional build dependency is necessary. I've refactored SimpleSocketServer to work with Jakarta Commons Daemon. If desired, I'd contribute a patch. Together with an init.d script it's pretty easy to start and stop a SimpleSocketServer. Regards, Stefan

1 0