June 2009 - logback-user - mailman3.qos.ch

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

capture system.err and system.out into log file
by gwen harold autencio 30 Jun '09

30 Jun '09

Hi , Is there a way to log the system.err and system.out in a log file, by using a fileappender instead of the console? Thanks

2 1

Trouble with Logback / JUL configuration
by Flavio Donzé 17 Jun '09

17 Jun '09

Hallo everyone Im having some trouble with JUL logging and was wondering if somebody has had the same issue or else a good solution. My problem is that logback settings seem to be ignored by JUL. So if I have the following example: <logger name="test"><level value="debug"/></logger> java.util.logging.Logger logger = java.util.logging.Logger.getLogger(test); logger.log(Level.FINEST, finest); logger.log(Level.FINER, finer); logger.log(Level.FINE, fine); logger.log(Level.INFO, info); Only the info will be logged. I found the following JavaDoc which is the root of the problem: <http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html#install%2 8%29> http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html#install() This handler will redirect jul logging to SLF4J. However, only logs enabled in j.u.l. will be redirected. For example, if a log statement invoking a j.u.l. logger disabled that statement, by definition, will not reach any SLF4JBridgeHandler instance and cannot be redirected Is there a solution or a workaround for this problem? Like a logging.properties which enables everything on trace level? Greets and thanks flavio ----- Flavio Donzé Software Engineer My Blog: http://swissdev.blogspot.com/

2 4

Oner more log level
by Trevor Leung 17 Jun '09

17 Jun '09

Hi, Is it possible to add one more log level, say, Fatal, above Error? I would like too seek your advice for the most convenient insert point. Thanks, Leung Wang Hei

2 1

Jboss + sLF4j + Spring,httpclient logger issue
by sridhar veerappan 17 Jun '09

17 Jun '09

Hi, I am new you slf4j using logback.xml, I am trying to integrate with jboss and spring web service, i am getting the debugger log, but DEBUG 1) httpclient.wire.header and 2) [org.springframework.web.servlet.DispatcherServlet] both the above mentioned debug logs are logged into jboss server server.log, instead of logging to my own log called somelog.log which i configure in logback.xml Anything we need to specially configure for these two jars, I think because jboss is loading their own lib, we need to took the jar files from the ear, for that we need to configure in logback.xml. But I am not sure how to configure to put those logs here in my own logger. <included> <appender name="SYSOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{ISO8601} [%t] %-5p %lo{40} - %m%n</pattern> </layout> </appender>  <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>${jboss.server.log.dir}/csm.log</File> <append>true</append> <BufferedIO>false</BufferedIO>  <ImmediateFlush>true</ImmediateFlush> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${jboss.server.log.dir}/csm.%d{yyyy-MM-dd}.log.gz</FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{HH:mm:ss.SSS} [%t] %-5p %-40lo{40} - %m%n</pattern> </layout> </appender> <logger name="com.air2web" additivity="false"> <appender-ref ref="FILE"/> <level value="debug" /> </logger> <logger name="httpclient.wire.header"> <level value="trace"/> </logger> <logger name="httpclient.wire" additivity="false"> <appender-ref ref="FILE"/> <level value="info" /> </logger> <logger name="httpclient.wire.header" additivity="false"> <appender-ref ref="FILE"/> <level value="debug"/> <level value="info" /> </logger> <logger name="org.springframework" additivity="false"> <appender-ref ref="FILE"/> <level value="ERROR"/> </logger> <logger name="org.springframework.web" > <level value="ERROR"/> </logger> <logger name="org.springframework.ws"> <level value="ERROR"/> </logger> but not reflecting in log. Could you please help me. Thanks in Advance Sridhar

1 0

Appenders
by Greg Flex 16 Jun '09

16 Jun '09

Hi Ceki and all, I figured the problem out so there's no need to answer my previous email. FYI: What was missing is the CallerData object that apparently needs to be defined.... Here is the code: (in addition to the code in previous message) CallerData callerData= new CallerData("somefilename.java", "foo", "methodFoo", 123); CallerData[] cda = new CallerData[1]; cda[0] = callerData; //then I added the callerData to the event... event.setCallerInformation(cda); This did the trick. I'm happy ;-) Gregory

1 0

Appenders
by Greg Flex 16 Jun '09

16 Jun '09

Hi Ceki, I have a question about the LoggingEvent object. I'd like to log some messages by "building" (populating constructor) of LoggingEvent object, then log it with my appenders. I saw some sample code on line and what I have at the moment is this: Logger log; LoggingEvent event; Object[] args = {"test", "test2"}; //<-- I'm not sure exactly what this is for? event = new LoggingEvent("class", (Logger) LoggerFactory.getLogger("SimpleSocketServer"), Level.toLevel("DEBUG"), "test message", null, args); log = (Logger) LoggerFactory.getLogger("testClassName"); log.callAppenders(event); This works with my "CONSOLE" appender and I can see messages (with the passed values) printed. I have also a "DB" - database appender, to which I'd like to write as well, but something doesn't work.... I see a couple of "initialization" log messages in the database, (like port and waiting for clients to connect etc.) but not the one I'm building myself, even though as I stated above I can see it in the console. What am I doing wrong? Here is part of my config file: <configuration> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <connectionSource class="ch.qos.logback.core.db.DataSourceConnectionSource"> <dataSource class="com.mchange.v2.c3p0.ComboPooledDataSource"> <driverClass>com.mysql.jdbc.Driver</driverClass> <jdbcUrl>jdbc:mysql://localhost:3306/logging</jdbcUrl> <user>greg</user> <password>greg</password> </dataSource> </connectionSource> </appender>  <root> <level value ="DEBUG"/> <appender-ref ref="CONSOLE" /> <appender-ref ref="DB" /> </root> </configuration> UPDATE: I just did a little test and I added an HTML FILE appender. I see all messages there too, just like in CONSOLE appender case. but still nothing in the database except for the initialization messages. Any suggestions? Thanks Gregory.

1 0

Need Custom Appender
by Krishnendra Nandi 13 Jun '09

13 Jun '09

Hi I am looking for an appender which takes the variables from within the thread to create a logfile I have multiple threads spawning from a main thread .This threads take a seperate file for processing and i need a log by that filename Any pointers to that would be helpful -- Thanks and Regards Krishnendra Nandi Phone :+919921514085 Skype :krish_nandi_78 Gtalk :krishnendra@gmail.com

2 1

Best practices to avoid deadlocks while logging
by Olivier Cailloux 13 Jun '09

13 Jun '09

Dear list, I recently had a deadlock problem related to logging and I am wondering if it comes from a problem in the logging framework (I must say I doubt it) or from the way I use logging, in which case I'd like to hear advices about how others avoid this kind of problems. The pattern is the following. (Please see hereby the java classes which might be clearer.) - In a class "Worker", a method "work()" locks the object instance of the class Worker to do some work and calls the logging framework to print the result (while still holding the lock). - In the same class "Worker", an other method "getStatus()" obtains the current status of the object instance of the class Worker and returns it as a String (method used for logging). That method locks the object at some point to make sure it reads consistent internal status information. - In an other class "Accessor", a method "access()" performs some work (not locking anything), then logs the status of an object of the class Worker by using its getStatus() method. Now the deadlock scenario is the following. - A thread "WorkerThread" is executing the method "work()". It has acquired the lock for the Worker object and has not reached the logging statement yet. - An other thread "AccessorThread" is executing the method "access()", and is executing the logging statement. AFAIU, logback console logger has some sort of "central" locking point: when a thread is logging, an other thread may not log in parallel (that seems good as the user does not want his different logging statements to be mixed together)... Thus, the following happens. - AccessorThread has a lock to the Logger, and waits to acquire the Worker lock to execute the synchronized block in getStatus(). - WorkerThread is holding that precise lock, and will never release it, because arriving at the logging statement in "work()", it starts waiting for the Logger lock acquired by AccessorThread. These two threads are caught in a deadlock. I feel the problem comes from not respecting the general rule that a block of code holding a lock should not call a method on an externally controlled object (possibly shared with other threads) whose locking behavior is unknown. (Note that both my code and the logging framework do not respect this rule, AFAIK.) So I should not have issued the log statement in my synchronized block in "work()". In my case, I can remove this logging statement from the synchronized block, but it is not clear to me whether it is always possible (or easy) to do so, especially if the thing you want to log depends on an internal state which might change as soon as you release the lock. An other way to solve that problem is to not use the parametrized message system in SLF4J. Indeed, it would disable the possibility of the AccessorThread to try to acquire the lock on Worker while being in the SLF4J method. I am wondering however if there is not a way that slf4j implementation (logback) release the lock on its logger, then gets the Worker lock, then re-acquire the lock on its logger only after having released the Worker lock, so that it has only one lock at a time? I tend to think that it would enable a user of the logging framework to pay no attention of the deadlock possibilities incurred by the logging framework, and to avoid him introducing subtle bugs with logging statements... But I may be wrong and I am not an expert in multithread programming. More generally speaking, what would be the advices from experienced programmers to avoid this problem? How do you log in a multithreading context? Also I am wondering if that (anti-)pattern could be documented on the logback page, to avoid others to do the same mistake as me? Or even on the SLF4J page, if it is not logback-specific? The attached classes provide a test case showing the deadlock scenario. The test fails reliably on my box. Thank you for any help. Olivier

3 7

Redeploying application on Tomcat 5.5 gives NullPointerException
by Thorbjørn Ravn Andersen 09 Jun '09

09 Jun '09

I just redeployed a WAR file on a Windows based Tomcat 5.5. server, after which reloading the login jsp-page resulted in the following stack trace: java.lang.NullPointerException ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:121) ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:437) ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:393) ch.qos.logback.classic.Logger.log(Logger.java:812) org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:120) org.apache.catalina.connector.Request.getRequestDispatcher(Request.java:1219) org.apache.catalina.connector.RequestFacade.getRequestDispatcher(RequestFacade.java:569) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:402) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144) com.foo.axsWHSweb.servlet.filters.LoggedInToAxsFreightFilter.doFilter(LoggedInToAxsFreightFilter.java:59) There is jcl-over-slf4j-1.5.5.jar, slf4j-api1.5.6, logback-classic 0.9.14 and logback-core-0.9.14 in the classpath. Is this a known and fixed issue (so I should upgrade all to the newest) or should I investigate? I believe there has been added an appender in logback.xml with a layout based on a class not present in the previous version of the war. -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"

2 3