Hi,

Bar my own lof statements there is nothing else bar the following in console other then the following on rollover:


21:45:12,655 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@2d86d8d1 - first clean up after appender initialization
21:45:12,655 |-INFO in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@2d86d8d1 - periodsElapsed = 336

....

21:45:12,752 |-WARN in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@2d86d8d1 - Unexpected periodsElapsed value 0

...

21:45:12,746 |-WARN in ch.qos.logback.core.rolling.helper.SizeAndTimeBasedArchiveRemover@2d86d8d1 - Unexpected periodsElapsed value 0


On Wed, Feb 20, 2013 at 9:55 PM, ceki <ceki@qos.ch> wrote:

Not all properties are printed on the console. The prudent mode is probably set correctly. Could you please also include the output on the console written when roll over occurs?


On 20.02.2013 22:50, Desmond Kirrane wrote:
Hi,

Nothing mentioned in the logs for prudent. Does this mean it just
ignores the prudent flag silently? Output below


21:45:11,367 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Could NOT find resource [logback.groovy]
21:45:11,367 |-INFO in ch.qos.logback.classic.LoggerContext[default] -
Found resource [logback-test.xml] at
[file:/..../target/test-classes/logback-test.xml]
21:45:11,465 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - Setting
ReconfigureOnChangeFilter scanning period to 30 seconds
21:45:11,466 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} -
Will scan for changes in [[/..../logback-test.xml]] every 30 seconds.
21:45:11,466 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - Adding
ReconfigureOnChangeFilter as a turbo filter
21:45:11,470 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
21:45:11,489 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
Naming appender as [CONSOLE_LOG]
21:45:11,540 |-INFO in
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming
default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for
[encoder] property
21:45:11,597 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
About to instantiate appender of type
[ch.qos.logback.core.rolling.RollingFileAppender]
21:45:11,600 |-INFO in ch.qos.logback.core.joran.action.AppenderAction -
Naming appender as [FILE]
21:45:11,626 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No
compression will be used
21:45:11,628 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will
use the pattern target/Test-%d{yyyy-MM-dd'T'HHmm}.%i.log for the active file
21:45:11,631 |-INFO in
ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1f91d41b - The date
pattern is 'yyyy-MM-dd'T'HHmm' from file name pattern
'target/Test-%d{yyyy-MM-dd'T'HHmm}.%i.log'.
21:45:11,631 |-INFO in
ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1f91d41b - Roll-over
every minute.
21:45:11,631 |-INFO in
ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@1f91d41b - Setting
initial period to Wed Feb 20 21:45:11 GMT 2013
21:45:11,633 |-INFO in
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming
default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for
[encoder] property
21:45:11,634 |-INFO in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file
name: target/Test-2013-02-20T2145.0.log
21:45:11,634 |-INFO in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is
set to [null]
21:45:11,637 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction
- Setting level of logger [com.mycompany] to ALL
21:45:11,637 |-INFO in
ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of
ROOT logger to ALL
21:45:11,637 |-INFO in
ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender
named [CONSOLE_LOG] to Logger[ROOT]
21:45:11,638 |-INFO in
ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender
named [FILE] to Logger[ROOT]
21:45:11,638 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - End of
configuration.
21:45:11,640 |-INFO in
ch.qos.logback.classic.joran.JoranConfigurator@6948c93e - Registering
current configuration as safe fallback point


On Wed, Feb 20, 2013 at 8:57 PM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>>

wrote:

    Hello,

    What is printed when you set the debug attribute of <configuration>
    to true? Example:

    <configuration debug="true">...</__configuration>



    --
    Ceki
    65% of statistics are made up on the spot


    On 20.02.2013 21:11, Desmond Kirrane wrote:

        Hi,

        I'm unsure from the documentation but does SizeAndTimeBasedFNATP
        support prudent mode.

        I have the following config:

              <appender name="FILE"
        class="ch.qos.logback.core.__rolling.RollingFileAppender">
                  <prudent>true</prudent>
                  <rollingPolicy
        class="ch.qos.logback.core.__rolling.__TimeBasedRollingPolicy">

        <fileNamePattern>target/Test-%__d{yyyy-MM-dd}.%i.log</__fileNamePattern>
                      <__timeBasedFileNamingAndTriggeri__ngPolicy
        class="ch.qos.logback.core.__rolling.SizeAndTimeBasedFNATP"__>
                          <maxFileSize>1KB</maxFileSize>
                      </__timeBasedFileNamingAndTriggeri__ngPolicy>


                      <maxHistory>30</maxHistory>
                  </rollingPolicy>
                  <encoder>
                      <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level
        %logger{36} -
        %msg%n</pattern>
                  </encoder>
              </appender>

        I've tried this and logback doesn't complain and file does
        rollover but
        just wondering is the prudent flag used?







--
Ceki
65% of statistics are made up on the spot
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user