August 2011 - logback-dev - mailman3.qos.ch

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.29-18-gc65a762
by git-noreply＠pixie.qos.ch 24 Aug '11

24 Aug '11

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via c65a76208681877c22de7a35c44dbade67919528 (commit) from 0ef4726a00390c62ef346ebfdd9673a8d4df4944 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=c65a76208681877c22de7a35… http://github.com/ceki/logback/commit/c65a76208681877c22de7a35c44dbade67919… commit c65a76208681877c22de7a35c44dbade67919528 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Aug 24 23:51:58 2011 +0200 better implementation for extraFolder method in TimeBasedRollingWithArchiveRemovalTest diff --git a/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java b/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java index 5f06454..7f75422 100644 --- a/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java +++ b/logback-core/src/test/java/ch/qos/logback/core/rolling/TimeBasedRollingWithArchiveRemovalTest.java @@ -29,10 +29,11 @@ import java.util.concurrent.TimeoutException; import java.util.regex.Matcher; import java.util.regex.Pattern; -import ch.qos.logback.core.CoreConstants; +import static ch.qos.logback.core.CoreConstants.DAILY_DATE_PATTERN; import ch.qos.logback.core.util.StatusPrinter; import org.junit.After; import org.junit.Before; +import org.junit.Ignore; import org.junit.Test; import ch.qos.logback.core.Context; @@ -106,6 +107,7 @@ public class TimeBasedRollingWithArchiveRemovalTest { System.out.println("randomOutputDir=" + randomOutputDir); // small maxHistory, many periods slashCount = computeSlashCount(MONTHLY_CROLOLOG_DATE_PATTERN); + int numPeriods = 40; int maxHistory = 2; @@ -113,15 +115,16 @@ public class TimeBasedRollingWithArchiveRemovalTest { + "}/clean.txt.zip", MILLIS_IN_MONTH, maxHistory, numPeriods); int beginPeriod = Calendar.getInstance().get(Calendar.MONTH); boolean extraFolder = extraFolder(numPeriods, 12, beginPeriod, maxHistory); + System.out.println("xxxx slashCount="+slashCount+", extraFolder="+extraFolder); StatusPrinter.print(context); check(expectedCountWithFolders(2, extraFolder)); } @Test public void dailyRollover() throws Exception { - slashCount = computeSlashCount(CoreConstants.DAILY_DATE_PATTERN); + slashCount = computeSlashCount(DAILY_DATE_PATTERN); doRollover( - randomOutputDir + "clean-%d{" + CoreConstants.DAILY_DATE_PATTERN + "}.txt.zip", + randomOutputDir + "clean-%d{" + DAILY_DATE_PATTERN + "}.txt.zip", MILLIS_IN_DAY, 5, 5 * 3); check(expectedCountWithoutFolders(5)); } @@ -144,9 +147,9 @@ public class TimeBasedRollingWithArchiveRemovalTest { sizeAndTimeBasedFNATP.setMaxFileSize("10000"); tbfnatp = sizeAndTimeBasedFNATP; - slashCount = computeSlashCount(CoreConstants.DAILY_DATE_PATTERN); + slashCount = computeSlashCount(DAILY_DATE_PATTERN); doRollover( - randomOutputDir + "/%d{" + CoreConstants.DAILY_DATE_PATTERN + "}-clean.%i.zip", + randomOutputDir + "/%d{" + DAILY_DATE_PATTERN + "}-clean.%i.zip", MILLIS_IN_DAY, 5, 5 * 4); // make .zip optional so that if for one reason or another, no size-based @@ -165,7 +168,22 @@ public class TimeBasedRollingWithArchiveRemovalTest { slashCount = 1; doRollover( - randomOutputDir + "/%d{" + CoreConstants.DAILY_DATE_PATTERN + "}/clean.%i.zip", + randomOutputDir + "/%d{" + DAILY_DATE_PATTERN + "}/clean.%i.zip", + MILLIS_IN_DAY, 5, 5 * 4); + checkDirPatternCompliance(6); + } + + + @Ignore + @Test + public void dailyChronologSizeBasedRolloverWhenLogFilenameDoesNotContainDirectory() throws Exception { + SizeAndTimeBasedFNATP<Object> sizeAndTimeBasedFNATP = new SizeAndTimeBasedFNATP<Object>(); + sizeAndTimeBasedFNATP.setMaxFileSize("10000"); + tbfnatp = sizeAndTimeBasedFNATP; + + slashCount = 1; + doRollover( + "clean.%d{" + DAILY_DATE_PATTERN + "}.%i.zip", MILLIS_IN_DAY, 5, 5 * 4); checkDirPatternCompliance(6); } @@ -294,9 +312,9 @@ public class TimeBasedRollingWithArchiveRemovalTest { // year is 2012, and not 2013 (the current year). boolean extraFolder(int numPeriods, int periodsPerEra, int beginPeriod, int maxHistory) { - int adjustedBegin = beginPeriod + 1; - int remainder = ((adjustedBegin) + numPeriods) % periodsPerEra; - return (remainder < maxHistory + 1); + // beginPeriod is 0 for JAN, 1 for FEB etc + int valueOfLastMonth = ((beginPeriod) + numPeriods) % periodsPerEra; + return (valueOfLastMonth < maxHistory); } int expectedCountWithFolders(int maxHistory, boolean extraFolder) { ----------------------------------------------------------------------- Summary of changes: .../TimeBasedRollingWithArchiveRemovalTest.java | 36 +++++++++++++++----- 1 files changed, 27 insertions(+), 9 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

http://logback.qos.ch/manual/configuration.html#loggerElement something wrong
by zuxiong lin 24 Aug '11

24 Aug '11

http://logback.qos.ch/manual/configuration.html#loggerElement Configuring loggers, or the <logger> element<http://logback.qos.ch/manual/configuration.html#loggerElement> each appender thus referenced is added to the named logger. Note that unlike log4j, logback-classic does not close or remove any previously referenced appenders before adding the new appender reference. In log4j version 1.2.16 , any previously referenced appenders are valid. <logger name="classlogger" additivity="false"> <level value="INFO" /> <appender-ref ref="MYINFO_FILE" /> <appender-ref ref="DEBUG" /> </logger> So, the manual is wrong.

1 0

[JIRA] Created: (LBCLASSIC-287) ThrowableProxy keeps common frames of cause-hierarchy
by Joern Huxhorn (JIRA) 23 Aug '11

23 Aug '11

ThrowableProxy keeps common frames of cause-hierarchy ----------------------------------------------------- Key: LBCLASSIC-287 URL: http://jira.qos.ch/browse/LBCLASSIC-287 Project: logback-classic Issue Type: Improvement Components: Other Affects Versions: 0.9.29 Reporter: Joern Huxhorn Assignee: Logback dev list The ThrowableProxy implementation is currently merely calculating the number of common frames but keeps the common frames of the cause stacktraces anyway. Wouldn't it make sense to remove the common stack trace elements of cause (and suppressed) exceptions before they are processed any further? This would reduce the size of the event upon transport and would probably also simplify calculation of packaging data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[JIRA] Created: (LBCLASSIC-286) Allow Threshold Filter to filter out levels above provided level
by Robert Elliot (JIRA) 22 Aug '11

22 Aug '11

Allow Threshold Filter to filter out levels above provided level ---------------------------------------------------------------- Key: LBCLASSIC-286 URL: http://jira.qos.ch/browse/LBCLASSIC-286 Project: logback-classic Issue Type: New Feature Components: Other Affects Versions: 0.9.30 Reporter: Robert Elliot Assignee: Logback dev list Priority: Minor It would be nice if a property could make the existing ThresholdFilter act in the opposite way - so that it response with NEUTRAL to levels equal to or _below_ the configured level, instead of equal to or above it. This would mean you could use two appenders with ThresholdFilters to split logging between error/warn on the one hand and info/debug/trace on the other, for instance. A new property (perhaps "revers"?) could be created with a default value of false and it would be backward compatible. (It's trivial to do yourself, of course, but it would be nice to have out of the box.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.29-17-g0ef4726
by git-noreply＠pixie.qos.ch 17 Aug '11

17 Aug '11

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 0ef4726a00390c62ef346ebfdd9673a8d4df4944 (commit) from 707298f12c4d6a5ae392a0c2c5bb488cbcc4f8ef (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=0ef4726a00390c62ef346ebf… http://github.com/ceki/logback/commit/0ef4726a00390c62ef346ebfdd9673a8d4df4… commit 0ef4726a00390c62ef346ebfdd9673a8d4df4944 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Aug 17 14:03:31 2011 +0200 typo fixes diff --git a/logback-site/src/site/pages/access.html b/logback-site/src/site/pages/access.html index 057d8c9..eba8f76 100644 --- a/logback-site/src/site/pages/access.html +++ b/logback-site/src/site/pages/access.html @@ -40,12 +40,12 @@ without much recoding was one of our main goals. In accordance with this strategy, logback-access builds on top of logback-core and can thus provide much of the functionality of logback-classic - but in the scope of HTPP-access logging. + but in the scope of HTTP-access logging. It should be noted that while logback-access requires logback-core, it is independent of logback-classic as well as slf4j. Just as importantly, logback-access artifact must be - installed at the container level, not at web-applcation level. It + installed at the container level, not at web-application level. It does not make sense to bundle logback-access.jar at the level of a web-application. ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/access.html | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-116) SyslogAppender should support RFC 5424
by Ralph Goers (JIRA) 16 Aug '11

16 Aug '11

SyslogAppender should support RFC 5424 -------------------------------------- Key: LBCLASSIC-116 URL: http://jira.qos.ch/browse/LBCLASSIC-116 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.16 Environment: All Reporter: Ralph Goers Assignee: Logback dev list The SyslogAppender supports RFC 3164. RFC 5424 has been released with obsoletes RFC 3164. See http://www.ietf.org/rfc/rfc5424.txt. At the very least the format of the timestamp has been changed. Either the SyslogAppender should be enhanced to comply with RFC 5424 or a new SyslogAppender should be created which does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 19

[JIRA] Created: (LBCLASSIC-146) SysLog Appender and Line Breaks = :(
by Ingo Siebert (JIRA) 16 Aug '11

16 Aug '11

SysLog Appender and Line Breaks = :( -------------------------------------- Key: LBCLASSIC-146 URL: http://jira.qos.ch/browse/LBCLASSIC-146 Project: logback-classic Issue Type: Bug Components: appender Environment: Debian 4 Etch, 64 Bit (most likely all enviroments) Reporter: Ingo Siebert Assignee: Logback dev list I'm using the SysLog appender and it works well. But I've problems with line breaks, especially for exceptions. Every strack trace line is written as new SysLog-Entry. Example: Aug 11 20:25:21 192.168.33.11 app2-cas org.osgi.framework.BundleException: The bundle class path entry "patch.jar"..." Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassPathEntry(ClasspathManager.java:168) Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.buildClasspath(ClasspathManager.java:145) Aug 11 20:25:21 192.168.33.11 app2-cas ^Iat org.eclipse.osgi.baseadaptor.loader.ClasspathManager.initialize(ClasspathManager.java:79) ... That's quire annoying if you want to filter or highlight entries. I think it's major, because there isn't a good workaround to filter/highlight syslog files. I'm using Logback 0.9.13, but I thinks it still exists in the trunk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

4 4

[JIRA] Created: (LBCORE-217) CyclicBufferFileAppender
by Pascal Leclercq (JIRA) 04 Aug '11

04 Aug '11

CyclicBufferFileAppender ------------------------ Key: LBCORE-217 URL: http://jira.qos.ch/browse/LBCORE-217 Project: logback-core Issue Type: New Feature Components: Appender Reporter: Pascal Leclercq Assignee: Logback dev list We mostly use "FileAppender" and/or RollingFileAppender. We have a debug level on certain logger just to be sure we'll be able to analyse what's goign wrong in case of an error. This cause huge amount of logs and slow down our application. It would be nice to combine CyclicBufferTracker (like in SMTPAppender) and FileAppender to be able to get only the n last lines before and error event occurs. I create a POC and end up to the conclusion that 50 % performance improvement (with the last 1000 lines). I would like to send you the POC but I can't upload here. Sample conf : <configuration> <appender name="FILE" class="fr.opensagres.CyclicBufferFileAppender"> <file>testFile.log</file> <append>true</append> <encoder> <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl"> <bufferSize>1000</bufferSize> </cyclicBufferTracker> </appender> <root level="DEBUG"> <appender-ref ref="FILE" /> </root> </configuration> regards -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 1