which version are you using?
We are using SLF4J 1.5.10 and Logback 0.9.18. We have reverted to log4j as it is working fine with log4j.
We have logback configured with this configuration:
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <Append>true</Append> <file>logs/process.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<FileNamePattern>logs/process-%d{yyyy-MM-dd_HH}.%i.log</FileNamePattern> <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <MaxFileSize>1MB</MaxFileSize> </TimeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout">
<Pattern>%date|%level|%logger{10}|%msg|%throwable{5}%n</Pattern> </layout> </appender>
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.
From the status we see this: 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]]