Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1060

If maxFileSize is not specfied in SizeAndTimeBasedFNATP, some logs are lost

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.1.2
    • logback-core
    • None
    • ubuntu 12.4.1, x64

    Description

      If maxFileSize is not specified when using SizeAndTimeBasedFNATP, then some logs are not written. Roughly 1 out of 10 logs are lost in my case, were I generate a lof logs (approx 15 per ms).

      Maybe the cause is that the threshold size is parsed as 0, and it's constantly reopening the file?

      Example:
      <timeBasedFileNamingAndTriggeringPolicy
      class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
      </timeBasedFileNamingAndTriggeringPolicy>

      thanks

      Attachments

        Activity

          People

            logback-dev Logback dev list
            dpinol Dani Pinyol
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: