April 2007 - logback-user - mailman3.qos.ch

An OSGi bundle for logback?
by John E. Conlon 14 Sep '07

14 Sep '07

Are there any plans for a logback OSGi bundle in the foreseeable future? ;-)

3 3

Unable to Initialize Logger in JDK1.4
by Brian Suksomwong 03 May '07

03 May '07

Hey all, I'm trying to test logback's JDK1.4 support, but am receiving a NoClassDefNotFoundException when running my test class. Test Class: import org.slf4j.Logger; import org.slf4j.LoggerFactory; public Test { public static void main(String args[]) { Logger log = LoggerFactory.getLogger(Test.class); System.out.prinln(log.getName()); } } My classpath includes: logback-classic-0.9.5-jdk14.jar logback-core-0.9.5-jdk14.jar slf4j-api-1.3.0.jar slf4j-jdk14-1.3.0.jar (just in case, but I receive the same error without it) When I try to run the class I receive the following stack trace: java.lang.NoClassDefFoundError: javax/management/ObjectName at ch.qos.logback.classic.joran.JoranConfigurator.addInstanceRules( JoranConfigurator.java:62) at ch.qos.logback.core.joran.GenericConfigurator.buildInterpreter( GenericConfigurator.java:83) at ch.qos.logback.core.joran.JoranConfiguratorBase.buildInterpreter( JoranConfiguratorBase.java:82) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:95) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:74) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure( GenericConfigurator.java:38) at ch.qos.logback.classic.util.ContextInitializer.configureByResource( ContextInitializer.java:24) at ch.qos.logback.classic.util.ContextInitializer.autoConfig( ContextInitializer.java:35) at ch.qos.logback.classic.util.ContextInitializer.autoConfig( ContextInitializer.java:46) at org.slf4j.impl.StaticLoggerBinder.initialize(StaticLoggerBinder.java:52) at org.slf4j.impl.StaticLoggerBinder.<init>(StaticLoggerBinder.java:44) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:39) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:57) at Test.main(Test.java:6) ... Removed 21 stack frames The javax/management package is not in JDK1.4, but is in JDK1.5. I think there is a binding issue happening; please help me solve this issue if possible. Thanks! -B-

3 3

wizard to create logback.xml
by dirk ooms 03 May '07

03 May '07

Hello list, i created a wizard that generates a logback.xml for logging to file, console, socket and/or email: http://wizardforge.org/pc?action=showVersion&id=72 enjoy, dirk

2 2

Dynamic (per Marker ?) file appender
by franck.routier＠axege.com 03 May '07

03 May '07

Hi, Would it be feasable to have a file appender that would log to a file dynamically created based on a Marker ? The use case I have in mind is I "launch jobs", and would like each job to have its own logging file (identified by an incremental job number for example). Would the use of marker to do so be feasable, be a good idea, imply to create a new appender class, be totally dumb :), ...? Thanks for your comments, Franck

2 1

logback and concurrency
by Xavier Hanin 03 May '07

03 May '07

Hi Logback community, I've read somewhere that logback is thread safe, but I would like some confirmation about that and what does it imply. So, first, is logback Logger implementation thread safe? Second, what is the recommended pattern to get a logger and use it: - create and store it in a static variable - create and store it in an instance variable - create and store it in a local variable Thanks in advance, Xavier -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/

2 1

Possible problem with markers...
by Joern Huxhorn 21 Apr '07

21 Apr '07

Hi guys. I did a quick'n'dirty conversion of Chainsaw to support LOGBack- instead of Log4J-Events. It works but I think I might have found a problem. It's also very well possible that I simply don't understand a LOGBack/SLF4J concept... While testing my changes I tried to send some Markers, too. The first problem I encountered was that the helper class org.slf4j.helpers.BasicMarker has a package-private constructor. I missed that MarkerFactory at that point and wrote my own SimpleMarker that did essentially the same as BasicMarker. This worked but Chainsaw would explode during event deserialization if my SimpleMarker class was not contained in the classpath. Is this expected behaviour or should LOGBacks SocketAppender always use BasicMarker instead of a user-implemented Marker class while serializing log events? I'm really not sure at all. After all, it *could* be worthwhile to use the applications original markers if there is some additional functionality beside tagging a log message... but isn't that in itself a misuse of the marker concept? Beside that, would it be possible to implement SLF4J's BasicMarker.toString somewhat like that: public String toString() { StringBuffer result = new StringBuffer(); result.append("BasicMarker[name=").append(name); if(markers.size()>0) { result.append(", {"); boolean first = true; for (Map.Entry<String, Marker> marker : markers.entrySet()) { if (first) { first = false; } else { result.append(", "); } result.append(marker.getValue()); } result.append("}"); } result.append("]"); return result.toString(); } So it would print contained markers instead of the current generic Object.toString()? This isn't really important but would be nice. Beside the mentioned problem I'm really very happy with LOGBack. I switched a major project a month ago and haven't had any problems beside the missing support in Chainsaw ;) . I especially love the ability to change the logging configuration during runtime in a reasonable way. Thanks for all your work, Joern.

2 1

logback.debug?
by dirk ooms 21 Apr '07

21 Apr '07

Hi, i would like to watch the 'internal' logging of logback to check whether logback is happy with the provided logback.xml (similar to using the log4j.debug in log4j), but i am not sure how to do this. i noticed the existence of StatusManager, but it's not clear to me how to use it. thanks for any guidance on this, dirk

2 1

Using logback in tomcat
by Michael Abato 17 Apr '07

17 Apr '07

I'm successfully using logback with Tomcat and have a small suggestion that will help people with complex deployments: look for logback-access.xml in system property catalina.base rather than catalina.home. Tomcat is intentionally setup such that multiple instances (java VMs) can be running off the same copy of the tomcat distribution and set up private CATALINA_BASE directories for server config, logs, temp space, etc. Such setups will naturally want to configure logback in CATALINA_BASE, not in the (potentially read-only) CATALINA_HOME. In cases where the user does *not* set CATALINA_BASE, it takes the same value as CATALINA_HOME (which is generally the same as TOMCAT_HOME). I've patched the source of LogbackValve.java to do this and it works well. The change of "catalina.home" to "catalina.base" is to trivial for a formal patch... On a related note, I've also configured tomcat to use log4j/logback for internal logging, which also works quite well. I noticed in a previous post you "don't recommend this at this time" and would like to know the reason(s). Routing *all* logging through one logger/one config, which in turn can separate "live" logs from rotated out "archive" logs in a separate directory is a godsend. I'm assuming it is because doing this requires mucking around with the tomcat startup scripts to replace ACL from the very beginning of the tomcat boot process. I'd already created a "boot" directory with a dynamic set of jar's and classes (for unrelated reasons) so switching ACL to log4j/logback was pretty trivial for me. Is there more to the reluctance than the fact that there is no "drop in" way to do it? If there's interest, I can tidy up my tomcat patch and post the details. -- View this message in context: http://www.nabble.com/Using-logback-in-tomcat-tf2890321.html#a8074672 Sent from the Logback User mailing list archive at Nabble.com.

2 2

SMTPAppender: authentication option missing?
by hstang 15 Apr '07

15 Apr '07

I'm trying to use the SMTPAppender but my SMTP server requires that I authenticate, and it appears that SMTPAppender do not provide the necessary authentication options. I also notice that SMTPAppenderBase uses Transport.send(), and no where does it use transport.connect(...) that accepts username and password. Just wondering if authentication would be supported, and why it was omitted in current version of logback. Thanks. -- View this message in context: http://www.nabble.com/SMTPAppender%3A-authentication-option-missing--tf3572… Sent from the Logback User mailing list archive at Nabble.com.

2 1

LocationInfo
by dirk ooms 15 Apr '07

15 Apr '07

Hello, In log4j LocationInfo was an attribute of several appenders (e.g. Socket, SMTP) to determine whether the 'expensive' location info should be determined. I couldn't find this attribute anymore in logback, what is logback's approach to this? I understand that for e.g. SMTPAppender this info could be derived from its contained Layout, but what about SocketAppender? cheers, dirk

2 1