Possible issue with time based rolling policy when using format %d{yyyy-MM-dd-a}

Hi all, My goal is to have my log file roll over twice a day (one to hold all AM logs, and one to hold all PM logs). Here is my configuration in logback.xml: <appender name="FILE" class=" ch.qos.logback.core.rolling.RollingFileAppender"> <file>/opt/apps/weblogs/TransactionReporting/TransactionReporting.log</file> <rollingPolicy class=" ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>/opt/apps/weblogs/TransactionReporting/TransactionReporting. %d{yyyy-MM-dd-a}.gz</fileNamePattern> </rollingPolicy> <encoder> <pattern>[%date] [%thread] [%level] [%mdc] [%logger:%method:%line]: %msg%n</pattern> </encoder> </appender> This configuration does result in the correct naming of archived log files (e.g. TransactionReporting.2011-03-22-AM.gz). However, the contents of the archived log files do not just contain half of the day's log entries. Whether the archived log file name ends in "...AM.gz" or "...PM.gz" these log files can contain log entries for both the morning and the evening. And, the same goes for the active log file (TransactionReporting.log). This active log file does not get archived when the time changes from AM to PM...so the log file contains log entries for both the morning and the evening. It seems as if the log file is rolling over only once a day, but I don't believe that it rolls over at the same time every day. Based on the modified date value on the archived files, it seems completely random as to when the file is actually rolled over. Any help or advice would be greatly appreciated. Thanks, Christopher White Sr. Programmer 1-617-772-2403 Christopher.White@bbh.com *************************** IMPORTANT NOTE*****************************-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ********************************************************************************
participants (1)
-
Christopher.White@bbh.com