September 2006 - logback-user

What's the benfits of using Logback over Log4j?
by Wesslan 24 Oct '06

24 Oct '06

I've just looked through the docs on your site (http://logback.qos.ch/shortIntro.html) I'm interested in the benefits of using Logback over Log4j but I can't find anything about this in the docs. Cheers

2 1

Re: What's the benfits of using Logback over Log4j?
by Ceki Gülcü 26 Sep '06

26 Sep '06

Hello, Logback is a rewrite of log4j based on the lessons learned during the years. Logback has a smaller memory footprint and is faster by a wide margin. It has much better error reporting capability and is generally more robust. Logback has support for markers which enables capabilities not found elsewhere. We will be documenting these capabilities in the near future. Just as imporantly, logback`s access module supports Tomcat and Jetty. Thus, many of the logging capabilites offered by the classic module are also available for http access logging. I hope this anwers your question, -- -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" http://www.qos.ch/shop/products/eclm/

1 0

What is the log4j.properties file equivalent for logback?
by Newcomb, Michael-P57487 22 Sep '06

22 Sep '06

Or, do I really have to do this: Logger logger = LoggerFactory.getLogger(MyAppWithConfigFile.class); LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); configurator.doConfigure(args[0]); Thanks, Michael

2 1

RE: [LOGBack-user] slf4j simple logger
by Ceki Gülcü 21 Sep '06

21 Sep '06

Actually, Jetty (the servlet container) uses it as its default logging system. They do not want debug statements to appear on the console. It is getting late. I'd like to rethink this with a clear head. At 10:45 PM 9/13/2006, Newcomb, Michael-P57487 wrote: >I was assuming slf4j-simple.jar would be used mostly by library developers >who don't want to fool around with including log4j/logback/jdk14 etc... >That is what I would like to use it for, but now I will have to create a >custom binding (or include one of the above packages) to see debug during >my tests? > >I will create the binding if necessary, but does it make sense to create a >slf4j-simple-debug.jar or something? > >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

2 1

Unable to use RollingFileAppender
by Samuel Doyle 15 Sep '06

15 Sep '06

Hello, I'm new to logback but read your documentation, I an not receiving any output to my logfile. Here is my configuration file, following this is the output from logback to the console. The only thing I notice is a warning about a TriggerPolicy. If this is the case do you have example syntax? --- <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="bitranlog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="append" value="true"/> <param name="MaxBackupIndex" value="1"/> <param name="file" value="/tmp/bitran.log"/> <param name="MaxFileSize" value="5MB"/> <layout class="ch.qos.logback.classic.PatternLayout"> <param name="pattern" value="%d [%-15.15t] %-5p %-30.30c{1} - %m%n"/> </layout> </appender> <logger name="org.accma.concentrator.services.bitran.BiTranService" additivity="false"> <level value="debug"/> <appender-ref ref="bitranlog"/> </logger> <root> <level value="debug" /> <appender-ref ref="bitranlog" /> </root> </configuration> --- Here is console output when using LoggerStatusPrinter: --- startElement [configuration] startElement [appender] startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@8c5ea2 startElement [param] startElement [param] LOGBACK: No context given for ch.qos.logback.core.util.PropertySetter@198defc startElement [layout] startElement [param] startElement [logger] startElement [level] startElement [appender-ref] startElement [root] startElement [level] startElement [appender-ref] INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch .qos.logback.core.rolling.RollingFileAppender] INFO in ch.qos.logback.core.joran.action.AppenderAction - Appender named as [bitranlog] WARN in ch.qos.logback.core.rolling.RollingFileAppender[bitranlog] - Please set a TriggeringPolicy for the RollingFileAppender named bitranlog INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [bitranlog] from t he object stack INFO in ch.qos.logback.classic.joran.action.LevelAction - org.accma.concentrator.services.bitran.Bi TranService level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[org.accma.concentrator.services.bitran.BiTranService] INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [bitranlog to Logger[root] Thanks, S.D.

3 8

Re: [LOGBack-user] slf4j simple logger
by Ceki Gülcü 13 Sep '06

13 Sep '06

Michael, The simple binding (slf4j-simple.jar) has always dropped logging request of level debug. It's now the expected behavior of that binding. You could easily modify it to log debug requests as well. Even better, create your own binding. Any of the above acceptable to you? At 03:28 PM 9/13/2006, Newcomb, Michael-P57487 wrote: >This logger should default to all levels on > >Thanks, >Michael -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

2 1

slf4j simple logger
by Newcomb, Michael-P57487 13 Sep '06

13 Sep '06

This logger should default to all levels on... Thanks, Michael

1 0

Re: [LOGBack-user] Message Format question
by Ceki Gülcü 08 Sep '06

08 Sep '06

Hello George, We chose the {} format instead of the more common {0} for performance reasons. One can parse format string quicker when there is no need to worry about order. Moreover, it is a *little* easier on the fingers to write logger.debug("hello {}", name); than to write logger.debug("hello {0}", name); There is also a higher risk making mistakes with the common, i.e. {0}, format. For example, logger.debug("hello {O}", name); logger.debug("hello {1}", name); logger.debug("hello {1}, I am {0}", yourName, myName); are all wrong. 'O' instead of '0', '1' instead of '0' and '1,0' instead of '0,1'. In short, we chose to optimize for the most common case by sacrificing less common usage patterns. As you say, the issue was debated previously, for example see: http://issues.apache.org/bugzilla/show_bug.cgi?id=16229 Does this answer your question properly? At 03:23 PM 9/8/2006, Harp, George wrote: >I have just started to explore logback and currently use log4j. >My first newb question has to do with the formating of messages chosen >(not critisizm) > >logger.errror( "this is an errr {} {}", new Object(), new Object{}); > >My not use the i18n syntax so log messages can be internationalized? >logger.error("this is err {0} (1}, new Object(), new Object()); > >then the first arguement can be read from properties files or db fro the >curent locale and be changable accordimng to lanhuage needs. >I have a feeling that ths was discussed already and I will be hearing the >results of that discussion. >Thanks for starting this project i do like the idea and plan to use it in >an upcoming project that I am involved in. -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://ceki.blogspot.com/

1 0

[ANN] Release 0.3
by Sebastien Pennec 08 Sep '06

08 Sep '06

September 8th, 2006 - Release of logback 0.3 Version 0.3 for all three logback modules is now available. This release offers several new Appenders, support for Mapped Diagnostic Context, improved tests and documentation In response to a bug report by Rickard Nilsson on the logback mailing list, a bug affecting parametrized logging was fixed. We also released a PropertiesTranslator webapp that converts log4j.properties files to joran configuration files (in XML format). You can download the modules, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the logback announce mailing list. To subscribe to logback-announce list, please visit the following URL. http://logback.qos.ch/mailinglist.html -- Sébastien Pennec sebastien(a)qos.ch Logback: the generic, reliable, fast and flexible logging library for Java.

1 0

Message Format question
by Harp, George 08 Sep '06

08 Sep '06

I have just started to explore logback and currently use log4j. My first newb question has to do with the formating of messages chosen (not critisizm) logger.errror( "this is an errr {} {}", new Object(), new Object{}); My not use the i18n syntax so log messages can be internationalized? logger.error("this is err {0} (1}, new Object(), new Object()); then the first arguement can be read from properties files or db fro the curent locale and be changable accordimng to lanhuage needs. I have a feeling that ths was discussed already and I will be hearing the results of that discussion. Thanks for starting this project i do like the idea and plan to use it in an upcoming project that I am involved in.

1 0