[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-330: -------------------------------------- There is no trigger as such. Once an OnConsoleStatusListener is registered, messages are printed as they are generated internally. The registration is done on line 43 of ConfigurationAction. Are you sure you are using logback 1.0.1? IS it possible for an older version of logback to be present on the class path?
no debug info printed when problem with FixedWindowRollingPolicy ----------------------------------------------------------------
Key: LBCLASSIC-330 URL: http://jira.qos.ch/browse/LBCLASSIC-330 Project: logback-classic Issue Type: Bug Components: joran Reporter: Antony Stubbs Assignee: Logback dev list Priority: Critical
This configuration causes no debug output to be displayed: {code} <configuration scan="true" scanPeriod="30 seconds" debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <target>System.out</target> <encoder> <pattern>| [%-5level] [%date{ISO8601}] [%logger] [%thread] [%X{akkaSource}] - %msg %rootException %n</pattern> </encoder>sdfsadf </appender> <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>server.log</file> <!-- only keep 3 --> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>server.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>1MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>| [%-5level] [%date{ISO8601}] [%logger] [%thread] [%X{akkaSource}] - %msg %rootException %n</pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT"/> <appender-ref ref="ROLLING"/> </root> </configuration> {code} If I remove the rolling file appender, debug output is shown. If I remove just the rollingPolicy, debug output is shown. If I remove just the <fileNamePattern>server-event.%i.log</fileNamePattern> the debug output is displayed and the exception about the missing field is shown. Seems related to http://jira.qos.ch/browse/LBCORE-38 and http://jira.qos.ch/browse/LBCLASSIC-62
-- 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