December 2008 - logback-user

question about start-up process and disabling auto-configuration
by Rob Ross 04 Dec '08

04 Dec '08

Is there a way to disable the auto-configuration at startup? One of the first things my app does is locate the right configuration file (logback.xml) to use for the current environment and calls doConfigure(). But, when the app first starts up, it automatically configures Logback and prints out the debug information to System.out. Since I immediately re-configure logback, this seems like a waste and the status messages are also extraneous. Is there a way to suppress the auto-configuration at startup so I can handle it myself? Or at least not print out those auto-configuration messages on System.out? Thanks! Rob

3 4

[SNMP] Appender
by Jonathan Dray 04 Dec '08

04 Dec '08

Hi, Is there any SNMP appender available to use with logback ? Thank you Regards, Jonathan

2 2

NoClassDefFoundError for ThrowableProxy?
by Rusty Wright 03 Dec '08

03 Dec '08

Why am I getting this warning in my log file? My WEB-INF/lib directory contains logback-classic-0.9.11.jar and that jar file contains ThrowableProxy.class. 2008-12-01 18:46:59 WARN ContainerBackgroundProcessor[StandardEngine[Catalina]] org.springframework.beans.factory.support.DisposableBeanAdapter.invokeCustomDestroyMethod:217, Invocation of destroy method 'close' failed on bean with name 'dataSource-db2': java.lang.NoClassDefFoundError: ch/qos/logback/classic/spi/ThrowableProxy

2 2

logging output duplicated
by Chris Cheshire 02 Dec '08

02 Dec '08

In my webapp I am trying to send emails only on errors, with everything else logged to a file. I am using logback under slf4j, with the log4j/slf4j bridge for the external libraries that normally use log4j. My configuration file is reloaded in the servlet context init (using the Joran configurator example from the documentation) so I can set some system properties used in the appenders (like the context name). The logging config has : <root level="ERROR"> <appender-ref ref="EMAIL" /> <appender-ref ref="FILE" /> </root> <logger name="foo" level="DEBUG"> <appender-ref ref="FILE" /> </logger> *Everything* not of log level ERROR coming from foo is getting logged twice. Why? I've pored over Chapter 2 of the documentation and it seems to describe the opposite of what is happening. The level for foo will ideally swap between DEBUG and INFO, but I can't have things logged twice all the time. How do I fix this? Thanks Chris

2 4

Context selectors useful?
by Ceki Gulcu 01 Dec '08

01 Dec '08

Hello all, I am in the process of fixing bugs related to context selectors in logback. However, while sometime ago I thought that context selectors were the wave of the future, I am increasingly skeptical about their usefulness (of context selectors). If you are using context selectors, could you please explain why? -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

5 12

Re: [logback-user] logging output duplicated
by Robert Elliot 01 Dec '08

01 Dec '08

foo appends all debug and above messages to the file and then because additivity is set to true by default on all loggers the message is passed to the root logger's appenders which will append them to the file (again) and to email. So you will get each message duplicated in the file. You could add the email appender to foo as well as root, and set foo's additivity to false. Then each message will only appear once in the file. (Incidentally, it sounds like you might be interested in my suggested alteration to logback here: http://jira.qos.ch/browse/LBCLASSIC-82 . It would make it relatively easy to prevent getting all those debug messages emailed to you! You could also add a filter to the email appender that only allows error messages to be appended.) ----- Original Message ----- From: "Chris Cheshire" <cheshirator(a)gmail.com> To: "logback users list" <logback-user(a)qos.ch> Sent: Sunday, 30 November, 2008 7:23:43 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: [logback-user] logging output duplicated In my webapp I am trying to send emails only on errors, with everything else logged to a file. I am using logback under slf4j, with the log4j/slf4j bridge for the external libraries that normally use log4j. My configuration file is reloaded in the servlet context init (using the Joran configurator example from the documentation) so I can set some system properties used in the appenders (like the context name). The logging config has : <root level="ERROR"> <appender-ref ref="EMAIL" /> <appender-ref ref="FILE" /> </root> <logger name="foo" level="DEBUG"> <appender-ref ref="FILE" /> </logger> *Everything* not of log level ERROR coming from foo is getting logged twice. Why? I've pored over Chapter 2 of the documentation and it seems to describe the opposite of what is happening. The level for foo will ideally swap between DEBUG and INFO, but I can't have things logged twice all the time. How do I fix this? Thanks Chris _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://qos.ch/mailman/listinfo/logback-user

1 0