[JIRA] Created: (LBCLASSIC-330) no debug info printed when problem with FixedWindowRollingPolicy
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Antony Stubbs commented on LBCLASSIC-330: ----------------------------------------- I can't edit my own issue?
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-330: -------------------------------------- Sorry, I can't edit it either. We will be installing a new version of jira hopefully giving us better usability. BTW, which version of logback is this?
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Antony Stubbs commented on LBCLASSIC-330: ----------------------------------------- Yes, the logging works, but no logback configuration debug information is output. Are you seeing that?
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-330: -------------------------------------- Yes, I was referring to the debug information. For completeness, here is the output I see. 20:02:09,794 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 30 seconds 20:02:09,795 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will scan for changes in [[C:\home\ceki\logback\logback-classic\src\test\java\ch\qos\logback\classic\issue\lbclassic330\logback.xml]] every 30 seconds. 20:02:09,795 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter 20:02:09,803 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 20:02:09,803 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 20:02:09,822 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 20:02:09,829 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 20:02:09,832 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ROLLING] 20:02:09,845 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@2393385d - No compression will be used 20:02:09,851 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 20:02:09,852 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ROLLING] - Active log file name: server.log 20:02:09,852 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ROLLING] - File property is set to [server.log] 20:02:09,853 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 20:02:09,855 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 20:02:09,855 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ROLLING] to Logger[ROOT] 20:02:09,855 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 20:02:09,855 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@15a62c31 - Registering current configuration as safe fallback point Which version of logback are you using?
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Antony Stubbs commented on LBCLASSIC-330: ----------------------------------------- 1.0.1 Where in the code is the debug dump printed?
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-330: -------------------------------------- As of logback 1.0.1, when the debug attribute of the conifiguration element is set to true, a OnConsoleStatusListener is registered with the context's StatusManager. Thus, the the answer to your question is <configuration ... debug="true">
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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Antony Stubbs commented on LBCLASSIC-330: ----------------------------------------- I'm sorry, I was asking for the line of code in the source code for logback that triggers the printout of the debug information, not the xml attribute that triggers it. As you can see I already have that.
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
[ 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
[ http://jira.qos.ch/browse/LBCLASSIC-330?page=com.atlassian.jira.plugin.syste... ] Antony Stubbs commented on LBCLASSIC-330: ----------------------------------------- Yes, quite sure. And I added a sysout line at the end of ConfigurationAction#begin that prints out the value of debugMode, and it is set to true, but nothing is printed. I'm still trying to track it down.
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
participants (2)
-
Antony Stubbs (JIRA) -
Ceki Gulcu (JIRA)