July 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

custom fields
by Mel T. 11 Aug '09

11 Aug '09

Hi, We have an in-house logger that we want to get rid of. This logger has application specific functionality. - We store logs in a database table - We have specific columns that put some very-frequently used context information - For that purpose, our logger has methods like this: log(String message, String someContextID1, String someContextID2, ...); - This is added to the DB with specific columns for someContextID1, someContextID2, etc... - We have a log viewer that allows to select logs based on that context information. So we need an appender that will continue to fill up that same table. If we move to a logger like logback, I am unsure how to best handle our application need. This first comes to mind: - Create our own facade that adds the specific log methods (like above) - This facade assembles these arguments into a parsable message given to sfl4j/logback - An in-house DBAppender can parse the message to extract the arguments and store them in the right column. Or is there a more natural way to do that? I looked at markers, MDC, but is is not clear to me if any of them would be good for that. Maybe MDC could be used that way: - Create our own facade that adds the specific log methods (like above) - This facade assembles these arguments and places them in MDC - An in-house DBAppender can read the MDC and store values in the right column. Also, is'nt adding another facade on top of SLF4J/logback a little too much? Since we may add out own facade, should'nt we directly use logback? -- Mel T.

4 3

slf4 with logback causes java.lang.OutOfMemoryError: Java heap space
by Mel T 31 Jul '09

31 Jul '09

Hi, I swiched our project to using SLF4J / logback. All projects and build files worked (we have 40 projects) until one of ant target failed with that error: java.lang.OutOfMemoryError: Java heap space If I switch it to using slf4j-simple, I do not get that memory error. If I use log4j binding, it works too. I will start digging more, but if this raises a possible answer, I would appreciate it. This ant target runs in eclipse to invoke a junit anttask, which runs a test class that uses dbunit. -- Mel T. -- View this message in context: http://www.nabble.com/slf4-with-logback-causes-java.lang.OutOfMemoryError%3… Sent from the Logback User mailing list archive at Nabble.com.

3 8

Problem with turbofilter for appender
by Ihsiak 30 Jul '09

30 Jul '09

Hello everybody I am trying to configure additional appender that would log only messages marked with specified Marker. Unfortunately when I put <turboFilter> block inside appender definition (in logback.xml file) I keep getting following errors: 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@5:66 - no applicable action for [turboFilter], current pattern is [[configuration][appender][turboFilter]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@6:11 - no applicable action for [marker], current pattern is [[configuration][appender][turboFilter][marker]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@7:15 - no applicable action for [onMismatch], current pattern is [[configuration][appender][turboFilter][onMismatch]] 12:27:48,312 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@8:12 - no applicable action for [OnMatch], current pattern is [[configuration][appender][turboFilter][OnMatch]] There's no such problem if I put <turboFilter> inside root <configuration> block (except that it doesn't do the job then). are turbo filters available only at root level (should I use evaluator filter instead)? related jars in the classpath: - logback-classic-0.9.16.jar - logback-core-0.9.16.jar - slpf4j-api.1.5.8.jar -- regards Bartosz Tomasik

2 2

about the config file. how to use the context-param on the logback.xml file?
by Y.Ding 30 Jul '09

30 Jul '09

Hi I want to know how to use the webapp's context-param on the logback.xml file.

1 0

foldering mechanism in timebasedrolling
by yigit darcin 29 Jul '09

29 Jul '09

Hello, I was about to ask how to do a timebasedrollingpolicy in RollingFileAppender, and I found out that if you give your FileNamePattern as /logs/%d{yyyy/ MM/dd/}log.log , you will have this wonderful folder hierarchy : logs/2009/05/05/log.log. and if you set can cause problems in Microsoft and Linux platforms but, that can be fixed easily. I am just sending this message to thanks for this very helpful library as it fixed my problems with Prudent mode also. Cheers, Yigit.

2 4

TimeBasedRollingPolicy and SizeBasedTriggeringPolicy
by yigit darcin 29 Jul '09

29 Jul '09

Hi, I have created a folder based logging system as the logs are created in the file system as : logs/2009/07/12/log.txt with this FileNamePattern: logs/%d{yyyy/MM/dd/}log.txt I am running in Prudent mode = true by the way. What I want to add is SizeBasedTriggeringPolicy for this logs, so I add the following: <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>3MB</MaxFileSize> </triggeringPolicy> but this is not affecting the current log file, how can achieve this SizeBasedTriggeringPolicy inside TimeBasedRollingPolicy ? Thanks and Regards, Yigit

1 0

Configuration initialization is too verbose
by cowwoc 28 Jul '09

28 Jul '09

Hi, When I try running my application that does not log anything I always see the following being dumped to stdout: 17:53:57,102 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 17:53:57,102 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/Users/Gili/Documents/jperipheral/java/netbeans/build/classes/logback.xml] 17:53:57,103 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath. 17:53:57,103 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/C:/Users/Gili/Documents/jperipheral/java/netbeans/build/classes/logback.xml] 17:53:57,103 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/C:/Users/Gili/Documents/jace/trunk/release/lib/jace.jar!/logback.xml] 17:53:57,155 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 17:53:57,155 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 17:53:57,157 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [RootConsoleAppender] 17:53:57,168 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [filter] on top of the object stack. 17:53:57,184 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing component [layout] on top of the object stack. 17:53:57,200 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [RootConsoleAppender] from the object stack 17:53:57,200 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to WARN 17:53:57,201 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [RootConsoleAppender] to Logger[root] I've got logback.xml in the default package containing: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender class="ch.qos.logback.core.ConsoleAppender" name="RootConsoleAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>warn</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%t %m%n</pattern> </layout> </appender> <root> <level value="warn"/> <appender-ref ref="RootConsoleAppender"/> </root> </configuration> I was under the impression that Logback only outputs this level of verbosity if I set debug="true" in the configuration file, but this isn't the case. Any idea what's causing this? Thanks, Gili -- View this message in context: http://www.nabble.com/Configuration-initialization-is-too-verbose-tp2465255… Sent from the Logback User mailing list archive at Nabble.com.

5 8

Tomcat logs, plus one log config per webapp
by Mel T. 28 Jul '09

28 Jul '09

Hi, I succeeded merging all logs there is in tomcat, webapps, and internal libraries by doing 3 things: -1 placing these JARs in commons/lib: logback-classic-0.9.16.jar logback-core-0.9.16.jar slf4j-api-1.5.8.jar log4j-over-slf4j-1.5.8.jar jul-to-slf4j-1.5.8.jar jcl-over-slf4j-1.5.8.jar 2- adding my logback.xml file to commons/classes 3- removing log4j and commons-logging JARs from my webapps. What I need to do now is have separate logging per webapp. It seems to me that this is where problems can start, according to this post: http://osdir.com/ml/java.logback.user/2008-07/msg00024.html Is this still the best way to do that? If so, is there any more details on how to write the "logback context loader" as suggested in there? BTW, it is hard for me to know if this is best targetted at SLF4J or LogBack lists... -- Mel T.

2 1

Trouble with C3P0
by Klaus Teller 27 Jul '09

27 Jul '09

Hi Folks, Nice work. My journey with logback started just today. So please bear with me. I want to do something i wasn't able to do with log4j: DB Appender + Pooling + MySQL. With log4j i had JDBCAppender+MySQL working. I managed to migrate this part to logback without a glitch. Now the pooling with C3P0 doesn't want to work. I get an exception saying "No suitable driver". What driver is it talking about? Here are the jars i got in my classpath: c3p0-0.9.1.2.jar logback-access-0.9.16.jar logback-classic-0.9.16.jar logback-core-0.9.16.jar mysql-connector-java-3.1.14-bin.jar slf4j-api-1.5.6.jar slf4j-api-1.5.8.jar Do i need something else? Thanks, Klaus. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

2 3