March 2013 - logback-user - mailman3.qos.ch

[Sifting Appender ] Programmatically
by M. MychaL 04 Apr '13

04 Apr '13

Hello, i have created a new configuration with some logger but without appender. I would like to create appender programmatically, to add them to their logger. And finally use MDC context to set which appender will log the messages... For moment, i have create FileAppender, Pattern & Encoder, Filter, Discriminator. I would like to link the FileAppender to SifitingAppender. How to do that ? there is no setparent or set*appender methods.... Any idea ? Thanks.

3 5

AUTO: Manfred Kuhlmann is out of office. (Rückkehr am 08.04.2013)
by manfred.kuhlmann＠steria-mummert.de 28 Mar '13

28 Mar '13

Ich werde ab dem 28.03.2013 nicht im Büro sein. Ich kehre zurück am 08.04.2013. I will be out of the office starting 28.03.2013. I will be back on 08.04.2013. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. Mit freundlichen Grüßen Manfred Kuhlmann Hinweis: Dies ist eine automatische Antwort auf Ihre Nachricht "Re: [logback-user] [Sifting Appender ] Programmatically" gesendet am 28.03.2013 17:17:33. Diese ist die einzige Benachrichtigung, die Sie empfangen werden, während diese Person abwesend ist. Steria Mummert Consulting AG Vorsitzender des Aufsichtsrates: Jürgen Sponnagel - Vorstand: Dr. Fritz Moser Gesellschaftssitz: Hamburg - HR B 61 116 Amtsgericht Hamburg - USt-ID-Nr.: DE118671351 Bitte denken Sie an Ihre Verantwortung gegenüber der Umwelt: Jede ausgedruckte E-Mail verursacht ca. 0,3 Gramm CO2 pro Seite. Diese Nachricht kann vertrauliche Informationen enthalten und ist allein für den Adressaten bestimmt. Wenn Sie nicht der rechtmäßige Empfänger sind, sind der Zugriff, die Weiterleitung, das Kopieren, die Veröffentlichung oder anderweitige Verwendung des Inhalts untersagt. In diesem Fall bitten wir Sie, den Absender unverzüglich zu informieren und diese E-Mail sowie sämtliche Kopien dieser E-Mail zu löschen. Der Inhalt von E-Mails innerhalb des Netzwerks kann überprüft werden, um die Übereinstimmung mit den geltenden Firmenrichtlinien und Vorgehensweisen zu gewährleisten. E-Mails können auf dem Transportweg von Dritten verändert werden, so dass deren Vollständigkeit und Echtheit nicht garantiert werden können. This e-mail communication may contain confidential information and is intended only for the recipient. If you are not the intended recipient you are not allowed to read, copy, distribute, publicize or use the content of this e-mail in any way. Please notify the sender and delete the e-mail and any copies of it. The content of e-mails within our network may be monitored to ensure compliance with company policies and procedures. E-mails can be alterated by third parties in transit. Therefore any e-mail is susceptible to alteration and its integrity cannot be assured.

1 0

SLF4J 1.7.5 with LogBack
by Frederic Conrotte 26 Mar '13

26 Mar '13

Hello Regarding performance improvement in SLF4J 1.7.5, as I do not see any LogBackLoggerFactory in the commits: https://github.com/qos-ch/slf4j/commit/4dc6af1af741d9419c33187 I'm wondering if it's worth upgrading if we use SLF4J + LogBack ?

2 1

Logback + Janino issue : NoSuchMethodError
by sss rrr 26 Mar '13

26 Mar '13

HI I see this error in my eclipse , could any one let me know what I am missing ? I am using mac and my ivy.xml has these dependencies: <dependency org="ch.qos.logback" name="logback-core" rev="1.0.11" conf="runtime,test"> <exclude org="org.codehaus.janino" module="janino"/> </dependency> <dependency org="ch.qos.logback" name="logback-classic" rev="1.0.11" conf="runtime,test"/>  <dependency org="org.codehaus.janino" name="janino" rev="2.6.1" conf="runtime,test"/> <dependency org="org.codehaus.janino" name="janino" rev="2.6.1" conf="source->source"/>  <dependency org="org.slf4j" name="jcl-over-slf4j" rev="1.7.2" conf="runtime,test"/>  <dependency org="org.slf4j" name="log4j-over-slf4j" rev="1.7.2" conf="runtime,test"/> Thanks Ramesh 11:16:21,797 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [com.homeaway] to INFO 11:16:21,797 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoSuchMethodError: org.codehaus.janino.ClassBodyEvaluator.setImplementedInterfaces([Ljava/lang/Class;)V at ch.qos.logback.core.joran.conditional.PropertyEvalScriptBuilder.build(PropertyEvalScriptBuilder.java:48) at ch.qos.logback.core.joran.conditional.IfAction.begin(IfAction.java:67) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:276) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:148) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:130) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:50) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:157) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:143) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:106) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:56) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:75) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:148) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:107) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:295) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:269)

2 1

Release of logback version 1.0.11
by Ceki Gülcü 25 Mar '13

25 Mar '13

Hello all, I am happy to announce the release of logback version 1.0.11. It should hit the Maven central repository within the next 2 hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter via the following account: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Can logging configuration files be separated when using ContextJNDISelector?
by Ville Hägg 21 Mar '13

21 Mar '13

Hi all, I need to clarify if I have understood logging separation correctly. I have almost the same scenario than described e.g. in this question: http://mailman.qos.ch/pipermail/logback-user/2010-March/001442.html. In my environment I have most of the application logic deployed to JBoss 7 as a JBoss module. Module have my shared libraries for common parts of the application as well as third party libraries (like Logback and Spring). My own custom shared implementations are using logging in a standard way by instantiating loggers as a static class variables. I am also having two war-applications which are using module described. Requirement is to have own logging context for each of the application. Which means applications should have their own log files, log levels and root loggers etc. I have tried to introduce JNDIBasedContextDiscriminator together with ShiftingAppender with no luck. My problem is that after my applications are initialized, it seems both of them is somehow sharing the same appenders. If I view status messages servlet, I can see that application B have initialized also RollingFileAppenders configured in application A's configuration file or other way round. RollingFileAppenders are wrapped inside SiftingAppender in both configuration files. Can anyone clarify to me can two applications using shared libraries have strictly separated configuration files which are introducing own loggers, appenders and logging levels? Or do I still have some kind of configuration problem with my setup? Thanks a lot, Ville

3 4

Groovy config and debug
by Christian Lipp 20 Mar '13

20 Mar '13

Hello! I would like to know if it is possible to enable Logback debug output via Groovy DSL. The corresponding XML is: <configuration debug="true"> ... </configuration> The online translator doesn't translate the debug option and when I look at https://github.com/qos-ch/logback/blob/master/logback-classic/src/main/groo… I think there is no handling of debug, but I am not sure. This question is also documented in http://stackoverflow.com/questions/15153662/logback-configuration-in-groovy… , but only as part of the post. Kind regards, CL

1 0

logback error when using in maven project
by marni srikanth 19 Mar '13

19 Mar '13

I am getting the following error when i am using maven, jboss 7.1.1. But i don't see when i tested it separately. Is there a fix to it? 17:24:23,675 ERROR [stderr] java.lang.ClassCastException: org.slf4j.helpers.NOPLoggerFactory cannot be cast to ch.qos.logback .classic.LoggerContext 17:24:23,681 ERROR [stderr] at com.zreflect.emyed.whiteboard.pubsub.EventLoggerAsync.logStart(EventLoggerAsync.java:116) 17:24:23,683 ERROR [stderr] at com.zreflect.emyed.whiteboard.pubsub.EventLoggerAsync.onDisconnect(EventLoggerAsync.java:62) 17:24:23,684 ERROR [stderr] at org.atmosphere.cpr.AtmosphereResourceImpl.onDisconnect(AtmosphereResourceImpl.java:817) 17:24:23,686 ERROR [stderr] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:761) 17:24:23,688 ERROR [stderr] at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:742) 17:24:23,690 ERROR [stderr] at org.atmosphere.cpr.AsynchronousProcessor.cancelled(AsynchronousProcessor.java:601) 17:24:23,691 ERROR [stderr] at org.atmosphere.container.BlockingIOCometSupport.cancelled(BlockingIOCometSupport.java:172) 17:24:23,693 ERROR [stderr] at org.atmosphere.cpr.AsynchronousProcessor$1.run(AsynchronousProcessor.java:119) 17:24:23,694 ERROR [stderr] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 17:24:23,696 ERROR [stderr] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) 17:24:23,698 ERROR [stderr] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) 17:24:23,699 ERROR [stderr] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) 17:24:23,703 ERROR [stderr] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) 17:24:23,707 ERROR [stderr] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) 17:24:23,715 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 17:24:23,716 ERROR [stderr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 17:24:23,718 ERROR [stderr] at java.lang.Thread.run(Thread.java:662)

2 2

SMTPAppender capturing disabled logging
by Chris Cheshire 18 Mar '13

18 Mar '13

This is my (relevant) config structure <configuration> <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> ... </appender> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> ... </appender> <root level="ERROR"> <appender-ref ref="EMAIL" /> <appender-ref ref="FILE" /> </root> <logger name="com.a" level="INFO" /> <logger name="com.a.b.c.IgnoreMe" level="OFF" additivity="false" /> </configuration> I have an SMTPAppender emailing me all errors generated by my webapp. One specific class is generating false positives so I want to turn them off. This has IgnoreMe not logging errors to "FILE", but errors are still making it to "EMAIL". How do I stop them going to the SMTPAppender too? Note : I have more loggers configured for external libraries set to INFO. I'd like to avoid putting appender references in every logger if possible. Thanks Chris

2 2

Release of logback version 1.0.9
by Ceki Gülcü 18 Mar '13

18 Mar '13

Hello all, I am happy to announce the release of logback version 1.0.10. It should hit the Maven central repository within the next 2 hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter via the following account: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

3 5