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

TimeBasedRollingPolicy - old logs present in current file
by Pradnya Gawade 20 Mar '11

20 Mar '11

Hi, I am trying with this for a long time but could not figure out the problem. My web application has to log to a log file but we want different category tags to be assigned to the logs from specific packages, although all log will go to the same physical log file. I create one appender per category with the required tag included in the encoder pattern. I have crated a filter per appender so it will only take the logs for that category and reject all other logs.Then I map the parent package of my web application source code with all the appenders that I have created for each category. I know this sounds complicated please bear with me. The category mapping I get in the logging is fine and as expected but I am facing other unexpected issue of files rolling over. I am using daily rollover policy. File gets rolled over properly but the current log file contains a copy of logs from archived file with new logs appended to it. I don't understand why it happens. I use o.9.20 version of logback. File rollover used to work fine before I categorized the log and when all the logs simply used to go to the same file without any category tagging associated. Please suggest what could be going wrong if you can think of some thing. Thanks in advance. My logback.xml looks like:  <appender name="LOGFILE-LPR" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="abc.log.LogFilterFacilityLPR"/> <file>${log.dir}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MM/dd HH:mm:ss} [%mdc{WEBAPP}] LPR %-5level %logger{25}:%L - %msg %n %ex{full}</pattern> </encoder> </appender>  <appender name="LOGFILE-USER" class="ch.qos.logback.core.rolling.RollingFileAppender"> <filter class="abc.log.LogFilterFacilityUSER"/> <file>${log.dir}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">  <fileNamePattern>${log.dir}.%d{yyyy-MM-dd}.log</fileNamePattern>  <maxHistory>30</maxHistory> </rollingPolicy> <encoder> <pattern>%date{MM/dd HH:mm:ss} [%mdc{WEBAPP}] USER %-5level %logger{25}:%L - %msg %n %ex{full}</pattern> </encoder> </appender> . . . .  <logger additivity="false" name="org.akaza.openclinica"> <level value="${logLevel}" /> <appender-ref ref="LOGFILE-OTHER"/> <appender-ref ref="LOGFILE-LPR"/> <appender-ref ref="LOGFILE-USER"/> <appender-ref ref="LOGFILE-MAIL"/> <appender-ref ref="LOGFILE-AUTH"/> <appender-ref ref="LOGFILE-UUCP"/> <appender-ref ref="LOGFILE-AUTHPRIV"/> </logger>

4 5

Restricting JMX control certain loggers?
by Steve Davis 17 Mar '11

17 Mar '11

Is it possible to configure logback so that most loggers' levels are modifiable via JMX, but restrict manipulation of certain loggers? E.g., enable the JMX Configurator for the root logger, but disable it for specific loggers with additivity="false"? It appears that the <jmxConfigurator /> element can only appear at the top level of a <configuration> block. The goal, for my application, is to allow user control of logging in the field, for debugging, but not allow anyone to disable certain loggers that handle security-related events. Preferably, those loggers wouldn't even show up in as attributes in jconsole. (This is a Java desktop app, not web.)

2 1

Re: [logback-user] SyslogAppender not logging Throwable message
by Steve Davis 17 Mar '11

17 Mar '11

Gustav, I had the same problem, and seemingly solved it by adding %ex{full} to my appender's suffixPattern. E.g.: <appender name="SYSLOG-DEFAULT" class="ch.qos.logback.classic.net.SyslogAppender"> <syslogHost>localhost</syslogHost> <facility>USER</facility> <suffixPattern>[%thread] %logger %msg%n%ex{full}</suffixPattern> </appender> Now, I'm still getting some extraneous syslog entries with the individual stack frames, in addition to those in the first syslog message, but that at least gives me something to work with: Mar 17 18:04:23.139 Mar 17 18:04:23.000 myhost user.err logtest.foo.bar.FooBar Exception caught... java.lang.Exception: This is a fake Exception at logtest.foo.bar.FooBar.spew(FooBar.java:28) at logtest.LogTest.main(LogTest.java:43) Caused by: java.lang.RuntimeException: This is a fake RuntimeException at logtest.foo.bar.FooBar.spew(FooBar.java:27) ... 1 common frames omitted Mar 17 18:04:23.139 myhost user.err at logtest.foo.bar.FooBar.spew(FooBar.java:28) Mar 17 18:04:23.139 myhost user.err at logtest.LogTest.main(LogTest.java:43) Mar 17 18:04:23.139 myhost user.err at logtest.foo.bar.FooBar.spew(FooBar.java:27) Mar 17 18:04:23.139 myhost user.err at logtest.LogTest.main(LogTest.java:43) "Exception caught..." was the String that I supplied in the logger.error call. I'm not sure how to get rid of the extraneous syslog entries after the main one, or why %ex{full} still result in "1 common frames omitted"... any suggestions out there? I'm still a logback newbie, but liking it, so far. Regards, Steve -- On Feb 4 at 14:30:18 2011, Gustav Karlsson wrote: > > Hi, > > We are using the SyslogAppender in logback 0.9.27 and are having > an issue with the logging of Throwables. > > When we are logging an entry like LOG.debug("My message", throwable), > "My message" and the throwable's stacktrace is appended to the log, > but not the throwable's message. Has anyone else experienced this and > know the cause? > > Regards, > Gustav

1 0

HOW TO: get UTC with offset printed in log file - not LOCAL time with offset
by bob.deremer＠thingworx.com 17 Mar '11

17 Mar '11

For the life of me I can't figure out the proper syntax for my file appender LAYOUT so that I get DATEs printed in UTC with the proper offset. Specifically, I want the format to be: YYYY-DD-MMTHH:mm:ss.SSS-05:00 I am using the following PATTERN_LAYOUT string: yyyy-MM-ddTHH:mm:ss.SSSZ By using the above LAYOUT, I can get the TZ offset, but the time is still in LOCAL time and the 'T' is removed. I'm sure this is something I'm doing wrong, so any help would be greatly appreciated. Thanks, Bob

1 0

Problem Using Custom Layout - No Output
by Taylor Venable 16 Mar '11

16 Mar '11

Hi there, I'm trying to use a custom layout and there's no output being generated when I log using it. My source code is at http://ideone.com/3jHWF and my configuration is at http://ideone.com/VC9iq - with just the first (by itself, currently commented out) encoder configuration, everything works just fine and log entries come out on the console. When I add the second (currently uncommented) encoder configuration, which wraps my custom layout, no output is emitted. The print statements inside my custom layout implementation don't appear either. Any ideas? I'm using version 0.9.28 - here's my Java version: java version "1.6.0_20" OpenJDK Runtime Environment (IcedTea6 1.9.7) (6b20-1.9.7-0ubuntu1~10.04.1) OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode) Thanks, -- Taylor C. Venable http://metasyntax.net/

1 1

TurboFilter thread-safety?
by César Álvarez Núñez 14 Mar '11

14 Mar '11

Hi all, I would like to known if TurboFilter is multithread-safe or not since the manual does not say anything about it. Reviewing https://github.com/ceki/logback/blob/master/logback-classic/src/main/java/c… have seen that a it makes use of a LinkedHashMap ( http://download.oracle.com/javase/6/docs/api/java/util/LinkedHashMap.html) which requires synchronization in case of multithread access. BR, /César.

2 2

Is it possible to be notified of log rolling events?
by Travis Hume 11 Mar '11

11 Mar '11

When A log is rolled I need to additionally write a <file>.md5 file. Is it possible to register a listener with logback to be notified of these types of events? Thanks -- Travis Hume | Senior Software Engineer |Brightcove Inc. 200 West Mercer Street, Suite 204 | Seattle, WA 98119

2 1

directories not being created during rollover
by Travis Hume 10 Mar '11

10 Mar '11

So close ... I'm programmatically building a logger and having some problems with logs being rolled correctly. The RollingFileAppender is configured like: fileName = "log/collector-events.log" rollingPolicy.fileNamePattern = "log/%d{yyyy/MM/dd/kk:mm}_collector-events_%i.log.gz Additionally, I've configured a SizeAndTimeBasedFNATP to trigger at a certain size. >From my reading and re-reading of the docs I'd expect log/collector-events.log to be rolled to log/2011/03/10/14:18_collector-events_0.log.gz Instead every minute I get a new file that looks like: log/collector-events.log82891979435328.tmp I've tried removing the compression (.gz) and standard configuration (logback.groovy) with the same result. I'm developing with logback-classic v0.9.28 on Ubuntu 10.10 and Java 1.6.0_21 thanks -- Travis Hume | Senior Software Engineer | Brightcove Inc. 200 West Mercer Street, Suite 204 | Seattle, WA 98119

1 0

patternlayout question
by David Tkaczyk 10 Mar '11

10 Mar '11

Is there a way to modify the pattern that is used by the logback runtime when it is logging messages during startup or configuration change. i.e. the messages that show up on the console when you include <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> in your configuration file. I'd like to have them match the pattern that I use for every other log message. Without a DTD or XSD it is hard to tell if I can do this via configuration XML. It is also not evident if I need to extend a class or implement a listener to implement this behavior on my own. I'm using 0.9.26... Thanks, Dave

2 2

parameterized logging
by Christopher Piggott 09 Mar '11

09 Mar '11

One other question: String user = "chris"; log.debug("User {} is requesting system logs", user ); the log output I get is: User {} is requesting system logs So, clearly, parameterized logging is not working. I'm using logback classic 0.9.27 with slf4j api 1.6.1 and a bunch of other stuff to catch j.u.l and j.c.l. It looks like parameterized logging has been there for a long time though. It should be just that simple, shouldn't it?

3 7