November 2007 - logback-user

Is there System properties configuration?
by thebugslayer 15 Jan '08

15 Jan '08

Hi, I read http://logback.qos.ch/manual/joran.html, it's only checking classpath for config logback.xml file. Is there a way to specify file location by System properties? Thanks, -- /bugslayer

5 8

Logback v1.0?
by Pascale, Peter H. 29 Dec '07

29 Dec '07

We're interested in logback as a replacement to log4j. One of the questions I get is what's the span in time and features between logback today (v0.9.8) and a v1.0 release. Yes, yes - that magical 1.0 carries a lot of weight with folks... In trolling the archives and documentation - I did see reference to the fact that the team believes in the value of sound documentation, and the team isn't comfortable with a v1.0 release without good documentation. Seems you are on track to rectify that, and I think the manual is great. Bug fixes - I'm having a hard time determining the remaining significant open defects. Would you characterize the 0.9.8 - 1 span as having a lot of fixes? Few but important fixes? And what about features. And I hate to dredge up this topic - but will we ever see a config file watch such as log4j, and that was requested recently. Not a deal breaker for us - given the arguments for JMX config reload. And the magical question - rough timing of v1.0? Before 2008? Thanks! Peter Pascale Pearson VUE **************************************************************************** This email may contain material confidential to Pearson. If you were not an intended recipient, please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************

2 1

Custom formatting of parameterized string
by RossJ 28 Nov '07

28 Nov '07

Hello, I would like to be able to use parameterized logging with a byte[] argument (formatted as a hex string). Obviously this doesn't work today because arrays don't have a toString() implementation. One way I can see to do this is to modify (or substitute) the ch.qos.logback.classic.pattern.MessageConverter class and base my implementation on the org.slf4j.helpers.MessageFormatter class. I can either build my own logback.jar or manipulate the classpath to make it active. Is there a better way to do this? Is customization of the parameterized formatting an area that is likely to be enhanced in future releases? Or is my requirement somehow unusual... /Thanks, Ross. -- View this message in context: http://www.nabble.com/Custom-formatting-of-parameterized-string-tf4882185.h… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Weird problem with MDC
by Roger Kapsi 26 Nov '07

26 Nov '07

I'm new to slf4j & logback and have a weird problem with MDC. I'm trying to run the SimpleMDC example that comes with logback but get the following unexpected output. Any idea what's wrong? Thanks -Roger java -cp logback-core-0.9.8.jar:logback-classic-0.9.8.jar:logback-examples-0.9.8.jar:slf4j-api-1.4.3.jar:. chapter7.SimpleMDC LOGBACK: No context given for ch.qos.logback.core.pattern.parser.Compiler@26e85f 12:43:59.539 [main] INFO chapter7.SimpleMDC - Check enclosed. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n12:43:59.540 [main] DEBUG chapter7.SimpleMDC - The most beautiful two words in English. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n12:43:59.540 [main] INFO chapter7.SimpleMDC - I am not a crook. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n12:43:59.540 [main] INFO chapter7.SimpleMDC - Attributed to the former US president. 17 Nov 1973. %PARSER_ERROR_X %PARSER_ERROR_X - %PARSER_ERROR_m%PARSER_ERROR_n

1 0

Best Practices and JMX Configuration
by Dale.Chapman＠medavie.bluecross.ca 22 Nov '07

22 Nov '07

I apologize if this has been covered already, but I have not been able to find it so far in the manual or the mailing list archive. My organization is in the middle of defining our logging standards and we are looking for some best practice information. We are intending to make use of JMX for management of the logger settings. 1 - In log4j, the standard practice that I saw was for developers to statically define a logger for each class instead of dynamically calling getLogger() for each logging message. Given the dramatic speed improvements in the getLogger() calls, is this still the recommended practice? 2 - When using the JMXConfigurator, do the existing loggers that have been defined get updated or are they discarded and new ones created? This is related to (1) above in that if new objects are created instead of updating existing, then use of a statically defined logger is not acceptable. Thanks in advance for the advice. Dale Chapman, Corporate Architect, Common Services Medavie 506-867-4430 dale.chapman(a)medavie.bluecross.ca ----------------------------------------------------------------------- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l’entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous puissions effectuer la correction à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu de la transmission originale ainsi que toute réponse ultérieure. Merci. -----------------------------------------------------------------------

1 0

log a whole transaction if a condition is satisfied
by Borja Ruiz 20 Nov '07

20 Nov '07

Hello, I'm writing an application and I would like to use logback features to model this scenario: My application processes client requests. Each request is identified by a transaction id, that appears on each log message. What I want to do is log all transaction messages if a condition in one transaction message is satisfied. For example, if my application generates those messages: [INFO] [transactionId=10] Searching... [INFO] [transactionId=11] Searching... [INFO] [transactionId=10] response=false [INFO] [transactionId=11] response=true [INFO] [transactionId=10] Finished [INFO] [transactionId=11] Finished And my condition is that variable "response" is set to true, my application output should be: [INFO] [transactionId=11] Searching... [INFO] [transactionId=11] response=true [INFO] [transactionId=11] Finished I've tried to figure out using buffered appenders to maintain log messages, filters to check conditions and triggers to decide when to log messages, but couldn't find a suitable solution. I would like to know if there is a way of solving this problem using logback provided features, or ideas to develop my own logback components. Thanks a lot!

1 0

stacktrace not printing
by Jim Endicott 15 Nov '07

15 Nov '07

I cannot figure out why the stacktrace of an exception is not printing. I am calling the debug method with 2 parameters, a string and a throwable but only the string is being logged. The Throwable is a org.springframework.web.util.NestedServletException object. Is there a configuration setting that I am missing? I am using slf4j-api-1.4.3 with logback 0.9.8 My logback.xml is: <configuration debug="true"> <appender name="F" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${catalina.base}/logs/service2.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%t %d{dd MMM yyyy HH:mm:ss} %5p %c{3}:%X{location} - %m %ex{full}%n</pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${catalina.home}/logs/service2.%d{yyyy-MM-dd}.log</file NamePattern> </rollingPolicy> </appender> <logger name="com.vizible"> <level value="DEBUG"/> </logger> <root> <level value="INFO"/> <appender-ref ref="F"/> </root> </configuration>

1 0

Logback always writes to the console
by Rene Reuter 14 Nov '07

14 Nov '07

Hi, I'm using Logback 0.9.8. I've configured my logback.xml file only with a FileAppender. But it always logs to the console too, why? I don't want to see the logs in the console. Do u know why? My logback.xml: <configuration> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <File>testFile.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{35} - %msg%n</Pattern> </layout> </appender> <root> <level value="debug" /> <appender-ref ref="FILE" /> </root> </configuration> That's the one from the sample's in the manual. Thanks May

2 4

Exception logging
by c_inconnu2 13 Nov '07

13 Nov '07

Hi, First, I was looking for a more recent log framework than log4j and I just discovered logback : thanks for this great piece of software. I am using it for a couple of hours now and I have a question about usage : With log4j i had : logger.error("Something went wrong because " + someReason, exception); But with logback (SLF4J) I have to keep this since the signature is : void org.slf4j.Logger.error(String msg, Throwable t) I would have thought that something like below had existed : void org.slf4j.Logger.error(String msg, Throwable t, Object[]) so i would have written logger.error("Something went wrong because {}", exception, someReason); Any advice ? Thanks David

2 1

Programmatic logback Configuration
by Chad La Joie 07 Nov '07

07 Nov '07

I have an application that ships with two logging configuration files; a default logback.xml file (DLF) included in the application JAR and a user-editable file (UEF) installed on the filesystem with other application configuration files. The DLF is used when the application is starting but before the code to read in the UEF is executed. My current code for reading in the UEF looks like this: LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); loggerContext.shutdownAndReset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); configurator.doConfigure(configuration.getInputStream()); loggerContext.start(); The behavior I'm seeing though is note quite what I expected. Assume the DLF contains a console appender and a logger definition for package "foo". The behavior I see when the UEF is loaded is: - Changes to the logger FOO (e.g. changes in the logging level, addition/removal of appenders, etc.) are picked up and become active. - Declaration of new appenders are picked up and become active (e.g. if a new file appender is defined I can see it creating the new log file). - Declaration of new loggers are *not* picked up. If, for example, a logger "bar" is defined and given the same console appender as "foo" no output from "bar" is sent to the console. Is this expected behavior? Is my code wrong (I've tried the same code without the start() or shutdownAndReset() method calls)? Any help would be appreciated. -- SWITCH Serving Swiss Universities -------------------------- Chad La Joie, Software Engineer, Security Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland phone +41 44 268 15 75, fax +41 44 268 15 68 chad.lajoie(a)switch.ch, http://www.switch.ch

2 3