We have logback configured with this configuration:
<br><br> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<br> <Append>true</Append>
<br> <file>logs/process.log</file>
<br> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<br> <FileNamePattern>logs/process-%d{yyyy-MM-dd_HH}.%i.log</FileNamePattern>
<br> <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
<br> <MaxFileSize>1MB</MaxFileSize>
<br> </TimeBasedFileNamingAndTriggeringPolicy>
<br> </rollingPolicy>
<br> <layout class="ch.qos.logback.classic.PatternLayout">
<br> <Pattern>%date|%level|%logger{10}|%msg|%throwable{5}%n</Pattern>
<br> </layout>
<br> </appender>
<br><br><br>The thing is that in our production environment (HP-UX) and
under heavy load, logging was working fine for a time, and suddenly
stop working.
<br><br>From the status we see this:
<br>INFO in c.q.l.co.rolling.helper.RenameUtil - Renaming file
[/gp/log/process.log] to [/gp/log/process.2009-12-16_11.22.log], ERROR
in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - IO failure
in appender java.io.InterruptedIOException: , WARN in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Attempted to
append to non started appender [FILE]., WARN in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Attempted to
append to non started appender [FILE]., WARN in
ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Attempted to
append to non started appender [FILE]., INFO in
c.q.l.co.rolling.helper.RenameUtil - Renaming file
[/gp/log/application.log] to [/gp/log/application.2009-12-16_11.log]]