March 2009 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCORE-91) Add new TriggeringPolicy class to cause one rollover at the start of each run
by Rick Beton (JIRA) 09 Aug '09

09 Aug '09

Add new TriggeringPolicy class to cause one rollover at the start of each run ----------------------------------------------------------------------------- Key: LBCORE-91 URL: http://jira.qos.ch/browse/LBCORE-91 Project: logback-core Issue Type: New Feature Components: Appender Affects Versions: 0.9.15 Environment: - Reporter: Rick Beton Assignee: Logback dev list Priority: Minor A new TriggeringPolicy will cause the logfile to rollover once at startup when used with FixedWindowRollingPolicy. This is useful during development so that the logfiles of recent runs are still available. Here is a candidate implementation. Note that * <append>true</append> is required - otherwise the previous file is overwritten before rollover happens, so rollover results in a useless list of empty files. * the documentation would need to warn users of the effect of running multiple applications concurrently (i.e. concurrent operating system processes) with the same logfiles. This applies even without the suggested feature. package ch.qos.logback.core.rolling; import java.io.File; import ch.qos.logback.core.rolling.TriggeringPolicyBase; /** * SimpleStartupTriggeringPolicy triggers a rollover once at startup only. This * is useful for preserving older logfiles during development. * * @author Rick Beton */ public final class SimpleStartupTriggeringPolicy<E> extends TriggeringPolicyBase<E> { private boolean fired = false; public SimpleStartupTriggeringPolicy () { // does nothing } public boolean isTriggeringEvent( final File activeFile, final E event ) { final boolean result = !fired && (activeFile.length() > 0); fired = true; if (result) { addInfo( "Triggering rollover for " + activeFile ); } return result; } } -- 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 4

[JIRA] Created: (LBCORE-76) Joran patterns should be case insensitive
by Ceki Gulcu (JIRA) 09 Aug '09

09 Aug '09

Joran patterns should be case insensitive ----------------------------------------- Key: LBCORE-76 URL: http://jira.qos.ch/browse/LBCORE-76 Project: logback-core Issue Type: Improvement Components: Joran Affects Versions: 0.9.12 Reporter: Ceki Gulcu Assignee: Logback dev list At present time, joran patterns are case sensitive. However, implicit actions are case insensitive. For coherence, joran patterns should be case insensitive. -- 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 3

[JIRA] Created: (LBCORE-61) TimeBasedRollingPolicy can not be used with any other triggering policies
by Szel Zoltan (JIRA) 07 Aug '09

07 Aug '09

TimeBasedRollingPolicy can not be used with any other triggering policies ------------------------------------------------------------------------- Key: LBCORE-61 URL: http://jira.qos.ch/browse/LBCORE-61 Project: logback-core Issue Type: Bug Reporter: Szel Zoltan Assignee: Logback dev list Priority: Critical If someone would like to have a time based rolling policy with a size based triggering policy, than the user will get a NullPointerException,: at ch.qos.logback.core.rolling.helper.Compress.GZCompress(Compress.java:130) at ch.qos.logback.core.rolling.TimeBasedRollingPolicy.rollover(TimeBasedRollingPolicy.java:142) at ch.qos.logback.core.rolling.RollingFileAppender.rollover(RollingFileAppender.java:91) at ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileAppender.java:116) at ch.qos.logback.core.WriterAppender.append(WriterAppender.java:124) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:81) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:282) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:266) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:487) at ch.qos.logback.classic.Logger.filterAndLog(Logger.java:479) The cause of this issue is the isTriggeringEvent method in the TimeBasedRollingPolicy which has a side effect, namely it prepares the file name of the file which is about to rotate. If someone uses a triggering policy other than the same TimeBasedRollingPolicy, than the isTriggeringEvent method will not be called, hence the elapsedPeriodFileName will be null, hence a null pointer exception will be thrown in the start of the compression or while renaming. Please modify the isTriggeringEvent to not have this side effect + the rollover logic to capture the time information from the current event. Thanks, Zoltan -- 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

2 5

[JIRA] Created: (LBCORE-90) RollingFileAppender calls triggeringPolicy.isTriggeringEvent(activeFile, event) with the same activeFile
by Valery Shorin (JIRA) 07 Aug '09

07 Aug '09

RollingFileAppender calls triggeringPolicy.isTriggeringEvent(activeFile, event) with the same activeFile -------------------------------------------------------------------------------------------------------- Key: LBCORE-90 URL: http://jira.qos.ch/browse/LBCORE-90 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.14 Reporter: Valery Shorin Assignee: Logback dev list In subAppend(...) method RollingFileAppender calls triggeringPolicy.isTriggeringEvent(activeFile, event) method with activeFileCache variable as first parameter, but activeFileCache variable initialized in start() method of RollingFileAppender and not changed anymore. -- 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

2 6

[JIRA] Created: (LBCLASSIC-114) add a context listener that automatically configures JMX
by Philippe Marschall (JIRA) 31 Jul '09

31 Jul '09

add a context listener that automatically configures JMX -------------------------------------------------------- Key: LBCLASSIC-114 URL: http://jira.qos.ch/browse/LBCLASSIC-114 Project: logback-classic Issue Type: New Feature Components: Other Reporter: Philippe Marschall Assignee: Logback dev list Priority: Minor Setting up logback JMX for a web application requires a bit too many manual steps. It is not enough to simply add <jmxConfigurator /> to the configuration file. You should also set the context path but often you can't know that in advance. In addition you still need to write custom code to [prevent memory leaks|http://logback.qos.ch/manual/jmxConfig.html#leak]. These issues could all be addressed by a custom context listener. <listener> <listener-class>ch.qos.logback.classic.selector.servlet.JmxEnabler</listener-class> </listener> Code attached. -- 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

2 4

[JIRA] Created: (LBCLASSIC-109) Logger allows TRACE messages when reset to DEBUG
by Andrew Ruch (JIRA) 21 Jul '09

21 Jul '09

Logger allows TRACE messages when reset to DEBUG ------------------------------------------------ Key: LBCLASSIC-109 URL: http://jira.qos.ch/browse/LBCLASSIC-109 Project: logback-classic Issue Type: Bug Environment: SLF4J 1.5.6 and Logback 0.9.15 Reporter: Andrew Ruch Assignee: Logback dev list Priority: Minor When reconfiguring the LoggerContext, TRACE messages are logged even when the Logger level is set to DEBUG. As Ceki pointed out, the following test reproduces the issue. @Test public void levelResetTest() { LoggerContext loggerContext = new LoggerContext(); Logger root = loggerContext.getLogger(LoggerContext.ROOT_NAME); root.setLevel(Level.TRACE); assertTrue(root.isTraceEnabled()); loggerContext.reset(); //Logger is reset to DEBUG assertFalse(root.isTraceEnabled()); <-- assertion fails assertTrue(root.isDebugEnabled()); } -- 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

2 1

[JIRA] Created: (LBCORE-59) Support for reconfiguration at runtime
by Michael Osipov (JIRA) 20 Jul '09

20 Jul '09

Support for reconfiguration at runtime -------------------------------------- Key: LBCORE-59 URL: http://jira.qos.ch/browse/LBCORE-59 Project: logback-core Issue Type: New Feature Components: Joran Affects Versions: 0.9.9 Reporter: Michael Osipov Assignee: Logback dev list Joran should support reconfiguration at runime like log4j's DOMConfigurator#configureAndWatch. -- 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 8

[JIRA] Created: (LBCORE-94) Rollover at launch time
by Ceki Gulcu (JIRA) 08 Jul '09

08 Jul '09

Rollover at launch time ----------------------- Key: LBCORE-94 URL: http://jira.qos.ch/browse/LBCORE-94 Project: logback-core Issue Type: Bug Components: Rolling Affects Versions: 0.9.15 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Rollover does not occur for old files when short lived application is restarted. This issue is related to LBCORE-26.However, the solution implemented in LBCORE-26 works if the RollingFileAppender has the File property set. This is not always the case. For instance <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>test.%d.log.zip</FileNamePattern> </rollingPolicy> <layout/> </appender> <root level="info"> <appender-ref ref="FILE"/> </root> Problem originally reported by Ch Pasha. See also http://www.qos.ch/pipermail/logback-user/2009-March/001030.html -- 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 4

[JIRA] Created: (LBCORE-60) Allow rolling based on time or file size
by Szel Zoltan (JIRA) 02 Jul '09

02 Jul '09

Allow rolling based on time or file size ---------------------------------------- Key: LBCORE-60 URL: http://jira.qos.ch/browse/LBCORE-60 Project: logback-core Issue Type: New Feature Components: Appender Affects Versions: 0.9.9 Reporter: Szel Zoltan Assignee: Logback dev list The rolling grouping file appender allows to roll over on a specific interval(TimeBasedRollingPolicy) or when the log file has reached a specific file size. But unfortunately Logback does not support both to use together. For example if i want to roll over every day but i also want to roll the file when it is greater than 100MB. Please consider adding this feature to Logback and feel free to contact me if further clarification is required. Thanks, Zoltan Szel -- 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 9

[JIRA] Created: (LBCORE-58) AppenderBase doAppend is synchronized causing significant performance problems when calling appenders.
by Ralph Goers (JIRA) 26 Jun '09

26 Jun '09

AppenderBase doAppend is synchronized causing significant performance problems when calling appenders. ------------------------------------------------------------------------------------------------------ Key: LBCORE-58 URL: http://jira.qos.ch/browse/LBCORE-58 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.10 Environment: All Reporter: Ralph Goers Assignee: Logback dev list Slow appenders cause Logback to be a significant bottleneck in the system. AppenderBase doAppend is synchronized to allow Appenders to be threadsafe. This is an extremely poor way to accomplish that. Many Appenders are slow since they are dealing with I/O of some kind but may be thread safe. Where they are not they should deal with the issue at the smallest granularity possible. AppenderBase must be changed to not be synchronized and any Appenders that are not thread safe should be modified appropriately. -- 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

2 6