July 2015 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1092) Add GEventEvaluator to logback access
by Matt Whipple (JIRA) 29 Jul '15

29 Jul '15

1 0

[JIRA] (LOGBACK-1092) Add GEventEvaluator to logback access
by Matt Whipple (JIRA) 29 Jul '15

29 Jul '15

1 0

logback console display not honoring threshold filter
by Todd Prickett 23 Jul '15

23 Jul '15

I have a logback.xml file containing the following: <appender name="console" class="ch.qos.logback.core.ConsoleAppender"> <param name="Target" value="System.out"/> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <encoder> <pattern>%date %-4relative [%thread] %-5level %logger{35} - %msg %n</pattern> </encoder> </appender> <appender name="debugfile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>debugFile.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>debugFile.%d{yyyy-MM-dd}.log</fileNamePattern> <MaxHistory>30</MaxHistory> </rollingPolicy> <encoder> <pattern>%date %-4relative [%thread] %-5level %logger{35} - %msg %n</pattern> </encoder> </appender> <appender name="infofile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>infoFile.log</file> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>infoFile_%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%date %-4relative [%thread] %-5level %logger{35} - %msg %n</pattern> </encoder> </appender> <appender name="warnfile" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>infoFile.log</file> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>WARN</level> </filter> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>warnFile_%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%date %-4relative [%thread] %-5level %logger{35} - %msg %n</pattern> </encoder> </appender> <root> <appender-ref ref="console"/> <appender-ref ref="debugfile"/> <appender-ref ref="infofile"/> <appender-ref ref="warnfile"/> </root> I want it to only show me INFO level logs or greater. So, I added the ThresholdFilter and set its level to INFO. Doing this worked for the RollingFileAppender (where one includes INFO and greater and the other includes DEBUG and greater).This didn't make a difference as the console statements continue to include DEBUG level statements. Can anyone tell me why?

1 0

[JIRA] (LOGBACK-1054) NullPointerException from RollingFileAppender
by Paulius Matulionis (JIRA) 23 Jul '15

23 Jul '15

1 0

JEP draft: Efficient API for Stack Walking / sun.reflect.Reflection replacement
by Jörn Huxhorn 17 Jul '15

17 Jul '15

Hi fellow devs. I’m cross-posting this to logback-dev and log4j-dev since I think both projects may benefit from staying up-to-date on this topic. This JEP discusses a public replacement API for the internal sun.reflect.Reflection which at least Logback is currently using (if available) in ch.qos.logback.classic.spi.PackagingDataCalculator. http://openjdk.java.net/jeps/8043814 https://bugs.openjdk.java.net/browse/JDK-8043814 This is just meant as a heads-up. Given that it’s not possible to just sign up for the openjdk JIRA to watch an issue I’m having a hard time staying in the loop. So more people keeping an eye on it won’t hurt. Discussion is supposed to happen on core-libs-dev(a)openjdk.java.net but the latest mail I could find about the topic was written on 2014-07-09... Cheers, Jörn.

1 0

[JIRA] (LOGBACK-898) AsyncAppender should be configurable to never block
by Jeff Wartes (JIRA) 16 Jul '15

16 Jul '15

1 0

JsonLayout for logback-access
by Espen A. Fossen 15 Jul '15

15 Jul '15

Hi I have been working on an JsonLayout for logback-access in the logback-contrib repo. Making it possible to log an IAccessEvent to json. It is built along the same structure as the JsonLayout from ch.qos.logback.contrib:logback-json-classic. To get some JUnit tests working I have added ch.qos.logback:logback-access:tests as a test dependency. This requires bumping the logback version to 1.1.3 for the whole logback-contrib repo. Repo with the new JsonLayout can be reviewed here: https://github.com/espenaf/logback-contrib I have also created a demo for showing the actual Json logging to console using some pages and jetty-maven-plugin. This can be checked out here: https://github.com/espenaf/logback-access-json-test Looking for some feedback, and a suggestion on how to proceed for getting this committed. Regards, Espen Fossen

1 0

[JIRA] (LOGBACK-898) AsyncAppender should be configurable to never block
by Gareth Davis (JIRA) 14 Jul '15

14 Jul '15

1 0

[JIRA] (LOGBACK-1091) Error occur when parsing logback.xml if the logback.xml declared external entities
by daniel.ruiqing.wang (JIRA) 14 Jul '15

14 Jul '15

1 0

[JIRA] (LOGBACK-1091) Error occur when parsing logback.xml if the logback.xml declared external entities
by daniel.ruiqing.wang (JIRA) 14 Jul '15

14 Jul '15

1 0