January 2013 - logback-user

issue with RollingFileAppender when File matches FileNamePattern
by Karl Pietrzak 09 Jan '13

09 Jan '13

Hello everyone! I've come across an issue with RollingFileAppender, but I'm not sure if it's us or logback. <configuration> <timestamp key="currentDate" datePattern="yyyy_MM_dd" /> <appender name="dataServiceRequestLog" class="ch.qos.logback.core.rolling.RollingFileAppender"> <param name="File" value="${the.log.dir}/${currentDate}.WebService.log"/> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>${the.log.dir}/%d{yyyy_MM_dd}.WebService.log</FileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <encoder class="ch.qos.logback.classic.encoder.PatternLayoutEncoder"> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level - %msg%n</pattern> </encoder> </appender> The curious part is that File matches the FileNamePattern for the rolling policy ("${the.log.dir}/${currentDate}.WebService.log" and "${the.log.dir}/%d{yyyy_MM_dd}.WebService.log"). Do you guys think that's OK? The intention is that there's a separate file for every day: - 2013_01_03.WebService.log - 2013_01_04.WebService.log - 2013_01_05.WebService.log - 2013_01_06.WebService.log The issue we're experiencing is seemingly random writes to old log files (e.g., today we saw writes to 2013_01_04.WebService.log). Could this be the rename problem? Perhaps there's a better way to achieve the desired functionality. Is this worth writing a unit test for in RollingFileAppenderTest.java? Any tips are greatly appreciated, thanks!

2 6

Bridging Log4J over SLF4J and the lack of Log4J Logger.setLevel()
by Mark Petrovic 07 Jan '13

07 Jan '13

[Originally posted on 12/26/2012, but it apparently did not make it to the list archives. msp] Hi. Thank you for SLF4J and Logback. I have this line of code that just today came in from an upstream dependency out of my control: private static final Logger logger = Logger.getLogger(FooImpl.class); static { logger.setLevel(Level.DEBUG); <<<<<<<<<<<<<<<< } Unfortunately, this is logging code I had been successfully bridging, but this setLevel() call on a Log4J logger breaks it. Do I have any elegant recourse beyond asking the developers of the line of code to not do this? Thanks. -- Mark

3 3

Pointing logback at a symbolic soft link
by Antony Stubbs 07 Jan '13

07 Jan '13

Loback doesn't seem to be able to see the file, it just carries on like there was no config file. And because of the debug system, I get no debug information. Can logback be pointed at a soft symbolic link file? ----- ___________________________ http://stubbisms.wordpress.com http://stubbisms.wordpress.com -- View this message in context: http://old.nabble.com/Pointing-logback-at-a-symbolic-soft-link-tp34863570p3… Sent from the Logback User mailing list archive at Nabble.com.

2 4

Logback design question
by Mark Petrovic 07 Jan '13

07 Jan '13

In Logback, Levels are final, meaning one cannot extend them to create new levels. I have no problem with this, but my users are wondering about it. Can you explain? Thank you. -- Mark

3 4

Incorrect rolling of log file
by Viens, Mike 03 Jan '13

03 Jan '13

I am using Logback to create a daily rolling log file. It does rename the existing log file and creates a new one, however it is not doing it correctly (or I am telling something incorrectly). Below is the logback.xml file I am using: <?xml version="1.0" encoding="UTF-8"?> <configuration> <timestamp key="today" datePattern="yyyyMMdd"/> <appender name="ScreenAppender" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>debug</level> </filter> <encoder> <pattern>%date{HH:mm:ss.SSS} %-5level %logger{20} [%file:%line] - %msg%n</pattern> </encoder> </appender> <appender name="UpdateAppender" class="ch.qos.logback.core.rolling.RollingFileAppender"> <append>true</append> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>info</level> </filter> <file>${CATALINA_HOME}/logs/update-server.log</file> <encoder> <pattern>%date{HH:mm:ss.SSS} %-5level %logger{40} [%file:%line] - %msg%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>update-server.%d{yyyy-MM-dd}.zip</fileNamePattern> <maxHistory>180</maxHistory> </rollingPolicy> </appender> <root level="debug"> <appender-ref ref="ScreenAppender"/> <appender-ref ref="UpdateAppender"/> </root> </configuration> The log file does get created as update-server.log. And when the day rolls over, the next generated message for logging does result in that log file being renamed, but not as I expect it to. The resulting name is update-server.log1161295506996864.tmp. And, the file itself is not ZIPped, just renamed. I would expect the file to be named update-server.20120103.log and to have that file ZIPped. Does anyone know why? As a second (minor) issue, I would like the original log file to be called update-server-YYYYMMDD.log, but when I tried to do that, the log file created stays the same and at midnight, the file is overwritten. I used the line below, but it appears that Logback does not increment the ${today} value: <file>${CATALINA_HOME}/logs/update-server-${today}.log</file> Mike Viens Sr. Software Engineer K-12 Technology 10911 White Rock Road, Suite 100 Rancho Cordova, CA 95670 D: (916)288-1651 M: (916)524-3663 E: mike.viens(a)pearson.com <mailto:michael.viens@pearson.com> Pearson Always Learning Learn more at www.pearsonschoolsystems.com <http://www.pearsonschoolsystems.com/>

1 0

Writing logs to ByteArrayStream programmatically
by Dan Filimon 02 Jan '13

02 Jan '13

Hi! I've been trying for the past couple of hours to log to a ByteArrayStream that I then convert to String and process. This is the code I came up with [1], that's sadly not working. I read an older e-mail about this [2], but I still can't get it working. I added some asserts to make sure I'm starting the objects properly and to my surprise the PatternLayoutEncoder's isStarted() method (actually the one in LayoutWrappingEncoder) always returns false, despite started being configurable. And, in any case, even removing the offending assert, I still can't write anything to the byte stream. It doesn't output anything now (after I call reset() on the LoggerContext object), otherwise it prints to the console (I don't have any config file set up). What am I doing wrong? Thanks! [1] https://gist.github.com/4436581 [2] http://old.nabble.com/Programmatic-configuration-of-OutputStreamAppender-tt…

1 0