February 2013 - logback-user

(no subject)
by Jeffrey B 17 Feb '13

17 Feb '13

http://www.luh-media.de/jq/evmyignj485flb12sy6bc.0l8wtejob?05q4o9oos60eywoi…

1 0

Level.toLocationAwareLoggerInteger
by Richard Sand 13 Feb '13

13 Feb '13

Just a minor observation - shouldn't Level.toLocationAwareLoggerInteger(Level level) be a static method (like its counterpart fromLocationAwareLoggerInteger)? Best regards, Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651

2 2

Messages in Syslog look corrupt through SyslogAppender
by Robert Kuhar 12 Feb '13

12 Feb '13

I have a SyslogAppender configured to send logging messages to Syslog on my localhost <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> <syslogHost>localhost</syslogHost> <facility>LOCAL0</facility> </appender> ... <appender name="DAILY_ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logs/dm.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logs/dm.%d{yyyyMMdd}.log</FileNamePattern> </rollingPolicy> <encoder> <pattern>%d{yyyy-MM-dd'T'HH:mm:ss.SSS} [%p] %c{2} DSN:%X{X-HTC-DEVICE-SN} APV:%X{X-HTC-APP-VERSION} RID:%X{X-HTC-REQUEST-ID} - %m%n</pattern> </encoder> </appender> ... <root level="info"> <appender-ref ref="STDOUT" /> <appender-ref ref="DAILY_ROLLING" /> <appender-ref ref="SYSLOG" /> </root> The messages are making it to syslog, but the text is screwed up. For example DAILY_ROLLING appender shows... 2013-02-12T12:37:58.363 [WARN] h.c.s.d.u.s.i.ProfileDataSource DSN:REK_20130212_1237 APV:com.htc.cs.dm;1.0.2219283162.452657.434767;mango RID:0001 - No Device Profile for serialNumber: REK_20130212_1237 ...but SYSLOG appender dorks it as... Feb 12 12:37:58 127.0.0.1 bobk-mbp.local [qtp763161750-30] htc.cs.service.device.ui.services.impl.ProfileDataSource No Device Profile for serialNumbe]: REK_20130212_1237 . The word "serialNumber" is presented as "serialNumbe]". Other messages are dorked in a similar manner; always one character at the end of some word gets replaced by a ']'. In my configuration, somehow, every syslog message is getting some single random character replaced with ']'. Where did I go wrong? Do I have to put an <encoder> on the Appender? I though that without an encoder the message went straight out. Is it my logback configuration screwing up, or is syslog to blame? So many questions, so little time. Thanks in advance for any insights you can offer. Bob

1 1

getThrowable() not part of IThrowableProxy?
by Richard Sand 12 Feb '13

12 Feb '13

Quick question - is there a reason why the method getThrowable() is not part of the IThrowableProxy interface? ThrowableProxy has it but since it's not part of the interface I need to cast to ThrowableProxy to access it. Purpose here is in a custom AppenderBase implementation, where I want to do some special processing if the ILoggingEvent has a throwable in it. I see that the IThrowableProxy provides its own methods of returning information about the underlying throwable object, but I've already got an existing library to handle the throwable object in the way I need to. It's not a huge deal (as said casting IThrowableProxy to ThrowableProxy does the trick) but it seems like it should be part of the interface. Thanks! Richard Sand | Managing Director PO Box 91824 | Austin | Texas 78709-1824 | USA Office: +1 888 612 8820 ext 02 | Fax: +1 866 304 3754 Mobile: +1 267 984 3651

1 1

commons-logging -> sl4j -> logback
by Kristian Lind 12 Feb '13

12 Feb '13

In a previous project I switched from commons-logging -> log4j to sl4j -> logback. One of the reasons I did that was the overhead in log4j when providing a object in the log... log.debug("This is a object" + object); would cause the object.toString to be called even debug was not enabled. Now I work on a new project that uses commons-logging -> sl4j -> logback (jcl-over-slf4j) My question is now, will this still call object.toString.. even debug is not enabled import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; .... log.debug("This is a object" + object); I would like to get rid of commons-logging and jcl-over.sl4j and only have sl4j and logback.

6 19

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

08 Feb '13

Ich werde ab dem 08.02.2013 nicht im Büro sein. Ich kehre zurück am 12.02.2013. I will be out of the office starting 08.02.2013. I will be back on 12.02.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] commons-logging -> sl4j -> logback" gesendet am 08.02.2013 09:24:27. 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 (Vors.), Dr. Reinhard Liedl 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

programmatic configuration to log to file
by Steve Prior 07 Feb '13

07 Feb '13

Based on some examples I cobbled together the following code to programmatically configure logback to write its output to a file (I don't like having config files around), but the output still goes to stdout in addition to the file. Can anyone give me a clue how I can only have the output go to the specific file and not stdout? Thanks Steve LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); FileAppender<ILoggingEvent> fileAppender = new FileAppender<ILoggingEvent>(); fileAppender.setContext(loggerContext); fileAppender.setFile(ConcurrencyExample.class.getSimpleName() + ".log"); PatternLayout pl = new PatternLayout(); pl.setPattern("%d %5p %t [%c:%L] %m%n)"); pl.setContext(loggerContext); pl.start(); fileAppender.setLayout(pl); fileAppender.start(); // attach the rolling file appender to the logger of your choice Logger logbackLogger = loggerContext.getLogger(ConcurrencyExample.class); logbackLogger.addAppender(fileAppender); // OPTIONAL: print logback internal status messages StatusPrinter.print(loggerContext); // log something logbackLogger.info("hello");

4 6

how configure OSGi-over-slf4j ?
by Cristiano Gavião 07 Feb '13

07 Feb '13

Hi, I would like to try OSGi-over-slf4j. I have installed it into an equinox product, set a low start level to it. but couldn't see any result. could someone point me to any example of its use? thanks Cristiano

2 1

TimeBasedRollingPolicy failed to rollover logfiles yesterday, but I see no RolloverFailure?
by Robert Kuhar 06 Feb '13

06 Feb '13

I have an appender configured like... <appender name="DAILY_ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logs/dm.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logs/dm.%d{yyyyMMdd}.log</FileNamePattern> </rollingPolicy> <encoder> <pattern>%m%n</pattern> </encoder> </appender> ... <root level="info"> <appender-ref ref="DAILY_ROLLING" /> <appender-ref ref="SYSLOG" /> </root> ...which typically has the effect of logging current data to the dm.log file and everyday at midnight rolling over the dm.log into a file named for the date, dm.20130205.log. Yesterday, however, for the first time ever, this rollover did not occur on any of my production servers. My dm.log file now has 2 days worth of data and I am wondering what went wrong? I expected to find a RolloverFailure or some indication of what went wrong to be laying in the dm.log file but there is nothing there. I have never seen this mechanism fail in either logback or log4j and am at a loss as to where to start troubleshooting. Where do I look to figure out what went wrong in logback? Am I correct in expecting some ch.qos.logback.core.rolling.RolloverFailure stacktrace to be appearing in my dm.log file or does it only go there if my app is correctly catching and logging all throwables?

1 0

Externalized Logback configuration for web applications
by Perryn Fowler 01 Feb '13

01 Feb '13

Hello, I have a logging use case that I would think was relatively common, but that does not seem to be supported particularly well by logback. I wanted to see what the logback community thinks/advises. The details of the use case - I am writing java web apps to be deployed to JEE web containers. - I want the logging config to be external to the wars, so that I can use the same wars in different environments, but configure logging differently. - I want to be able to deploy several different wars to the same web container and have them use different logging configurations. The logback documentation seems to push towards either packaging the logback config in the wars, or sharing an external logging config between them. (Whereas I want separate external logging configuration for each war) I hope that makes sense. The JNDI support described here: http://logback.qos.ch/manual/loggingSeparation.html looks like it might be of use, but it does seem to require that the config files are placed in WEB-INF/classes and I would prefer they are completely external to the war. I have found a number of people who have coded up their own solutions, notably: http://blog.iprofs.nl/tag/logback/ and https://bowerstudios.com/node/896 That doesn't look too bad, but wondering what the community thinks of these approaches -- ----------------------- Perryn Fowler

6 10