February 2010 - logback-user

org.slf4j.impl.StaticLoggerBinder.SINGLETON
by Rusty Wright 25 Oct '11

25 Oct '11

I'm unable to create a bugzilla account at http://bugzilla.slf4j.org/createaccount.cgi Could someone enter this bug report for me? If I change my version of logback to 0.9.11 I don't get this. I get it when I use logback version 0.9.13. I'm using version 1.5.5 of slf4j. Thanks Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest; nested exception is org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:35) at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:330) at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:62) at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:81) at org.testng.internal.TestNGClassFinder.<init>(TestNGClassFinder.java:114) at org.testng.TestRunner.initMethods(TestRunner.java:281) at org.testng.TestRunner.init(TestRunner.java:227) at org.testng.TestRunner.init(TestRunner.java:189) at org.testng.TestRunner.<init>(TestRunner.java:138) at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:477) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:244) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:821) at org.testng.TestNG.runSuitesLocally(TestNG.java:788) at org.testng.TestNG.run(TestNG.java:708) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:26) ... 23 more Caused by: java.lang.IllegalAccessError: tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory at org.slf4j.LoggerFactory.staticInitialize(LoggerFactory.java:83) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:73) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:272) at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.<init>(AbstractTestNGSpringContextTests.java:77) at edu.berkeley.ist.cars.net.email.EmailTest.<init>(EmailTest.java:21) ... 28 more

4 5

Separating the logging-output of libraries in tomcat/shared
by Achim Wiedemann 02 Mar '10

02 Mar '10

Hey everybody, just wanted to port our application from commons-logging / log4j to slf4j / logback. Unfortunately I stumbled upon some problems when separating the logging-output from different webapps (using the JNDIContextSelector). As long as you only use logging from classes inside the webapp, everything works fine. But as soon as you've got classes in tomcat/shared which use logging, you run into trouble: All logging output of the shared classes (e.g. Spring) are directed to the logger-context of the webapp which first loads the (shared) class. Example: Let's say you've got webbapp [A], webbapp [B], and Spring in tomcat/shared. Now both webapps use Spring. If webapp [B] first accesses any classes of Spring, all output of Spring will be directed to the log-file of [B], no matter from which webapp Spring is used. This is because static Logger references are used in Spring (which is commonplace) and are initialized with the context of webapp [B]. The issue is already described very well in the logback JIRA: http://jira.qos.ch/browse/LBCLASSIC-166 I wondered if anyone can make a suggestion how to deal with this. Any advice, tricks or magic is welcome. ;) Thanks a lot, Achim

4 9

About DBAppender
by Mohammad Firoj Haider 28 Feb '10

28 Feb '10

Hi, I am new in Logback framework. I want to use mysql database to store my log. So I have set my logback-test.xml file in the following way: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DriverManagerConnectionSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <url>jdbc:mysql://localhost:3306/testlogback</url> <user>root</user> <password>test</password> </connectionSource> </appender> <root level="debug"> <appender-ref ref="DB" /> </root> </configuration> After that I created a database which is called "testlogback". I have two simple java classes. The code snippet is: public class TestLogger { public static void main(String[] args){ Logger logger = LoggerFactory.getLogger("com.lashpoint.TestLogger"); LoggerContext lc=(LoggerContext) LoggerFactory.getILoggerFactory(); StatusPrinter.print(lc); logger.debug("Test start"); System.out.println("Hello World Logback"); SalaryTestLogger test=new SalaryTestLogger (); test.setHour(0); test.setSalary(100); System.out.println("Division: "+test.getSalary()); logger.debug("Test end"); } } public class SalaryTestLogger { ............................ public SalaryTestLogger(){ logger=LoggerFactory.getLogger("com.lashpoint.SalaryTestLogger "); } ................ .......................... } After running the code, I got the following output (However, I put StatusPrinter.print(lc) to see internal state). Driver name=MySQL-AB JDBC Driver Driver version=mysql-connector-java-5.0.7 ( $Date: 2007-03-09 22:13:57 +0100 (Fri, 09 Mar 2007) $, $Revision: 6341 $ ) supportsGetGeneratedKeys=true true 12:08:37,312 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [file:/E:/DevTools/projects/Test/LogbackTest/src/com/lashpoint/logger/logback-test.xml] 12:08:37,421 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 12:08:37,421 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.db.DBAppender] 12:08:37,437 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DB] 12:08:37,468 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [connectionSource] on top of the object stack. 12:08:37,812 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [DB] from the object stack 12:08:37,812 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 12:08:37,812 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DB] to Logger[ROOT] Hello World Logback Salry Per Hour: 0.0 The MOST INTERESTING THING is that, it did not log anything to logging_event, logging_event_exception, logging_event_property tables. So I think I am missing something. I would be glad if someone kindly help me to solve this issue. -- Thanks Mohammad Firoj Haider

1 0

(no subject)
by Gilles Gaillard 23 Feb '10

23 Feb '10

Hi, I'm new to logback and would like to know if the following already exist / is possible, i searched the mailing list but did not find this. I've a GUI application performing usual logging through logback (that's ok) and would ensure that any unexpected failure(s) be logged. For example, unexpected errors occuring on the swing EDT go the std err. Usually I would do this by redirecting the standard out/err streams to some file output. Note also that I would like to ensure that logs from different threads will log properly. For example, stack traces should not be mangled by other logs. I wonder it is possible to do this through the logback configuration. If not what would be the best way. Thanks, -- Gilles

4 5

Redirect stderr-stdout standard streams
by Gilles Gaillard 23 Feb '10

23 Feb '10

Hi, I'm new to logback and would like to know if the following already exist / is possible, i searched the mailing list but did not find this. I've a GUI application performing usual logging through logback (that's ok) and would ensure that any unexpected failure(s) be logged. For example, unexpected errors occuring on the swing EDT go the std err. Usually I would do this by redirecting the standard out/err streams to some file output. Note also that I would like to ensure that logs from different threads will log properly. For example, stack traces should not be mangled by other logs. I wonder it is possible to do this through the logback configuration. If not what would be the best way. Thanks, -- Gilles

1 0

Status of Jira LBCORE-131?
by laboo 19 Feb '10

19 Feb '10

Hello logbackers, I've been bitten by the issue detailed in Jira as LBCORE-131. It's a fairly serious bug as it causes a loss of data, but there have been no replies to the issue as yet. I'm just curious if incorporating the suggested fix is on the todo list? http://old.nabble.com/-JIRA--Created%3A-%28LBCORE-131%29-SizeAndTimeBasedFN… I apologize in advance if this is not the correct way to ask about Jira issues. Please advise if I'm out of order here. Thanks, Mark -- View this message in context: http://old.nabble.com/Status-of-Jira-LBCORE-131--tp27657302p27657302.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Reduce to 0, logback startup output message...
by José Juan Montiel 18 Feb '10

18 Feb '10

Hi, i read few post about how to reduce de verbosity of startup messages o logback. In "Automatic printing of status messages in case of warning or errors" of [1] write... Instead of invoking StatusPrinter programmatically from your code, you can instruct the configuration file to dump status data, even in the absence of errors. To achieve this, you need to set the debug attribute of the configuration element, i.e. the top-most element in the configuration file, as shown below. Please note that this debug attribute relates only to the status data. It does not affect logback's configuration otherwise, in particular with respect to logger levels. (If you are asking, no, the root logger will not be set to DEBUG.) in special... Please note that this debug attribute relates only to the status data. It does not affect logback's configuration. The question is? How can i reduce to 0 "logback's configuration" messages? This is a little problen, because o tomcat, this messages goes to catalina.out and make that other problems on startup where dificult to find. Any idea? Thanks. [1] http://logback.qos.ch/manual/configuration.html -- Jose Juan Montiel Martinez Eurobits Technologies Calle Musgo 3, 1ª Planta 28023 Madrid T +34-917080300 F +34-913077480 josejuan.montiel(a)eurobits.es http://www.eurobits.com

1 0

How to output all errors to console, and errors+mesgs to logfile?
by Rob 14 Feb '10

14 Feb '10

Hello, I'm a new user and struggling to achieve the following: 1) All "error" messages must go to stdout and a logfile. 2) Based on com.example.myclass level settings, messages also go to logfile. My problem is I can't get both requirement 1 and 2 working simultaneously. The following results in debug messages going to the console. Using additivity="false" results in errors from com.example.myclass not going to the console. Any suggestion is welcome! <configuration> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> ... <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> ... <logger name="com.example.myclass" level="debug"> <appender-ref ref="ROLLING"/> </logger> <root level="error"> <appender-ref ref="CONSOLE"/> <appender-ref ref="ROLLING"/> </root> </configuration> Thanks, Robert

3 3

Logback Eclipse Plugin Status?
by Jeff Jensen 08 Feb '10

08 Feb '10

The download page [0] has had "It will be upgraded in the coming weeks." on it for quite a few months. Is there a status update to share? Is it being discontinued? Regarding the statement "It expects logback version 0.9.9.", will it fail with 0.9.18? I could not find a list of Eclipse versions it should work with. Anyone using it with Galileo? I was about to just "try it", but have had problems in the past trying to recover from incompatibilities, so hesitate. Also, as a feature, we were hoping for a simple picklist of log levels (or regexp to apply to the view) to real-time filter the view vs drop incoming messages. Any plans for a plugin update site vs manual install? [0] http://logback.qos.ch/download.html

7 16