[logback-user] Handling file access errors

David Roussel nabble at diroussel.xsmail.com
Tue Oct 1 13:58:06 CEST 2013


You can create your own appender which, on error, can signal your application to stop. 


> On 30 Sep 2013, at 20:40, Gabriel Soto <gabsoto at gmail.com> wrote:
> Good afternoon,
> We are using Logback in a security sensitive application.
> The logging configuration normally includes a RollingFileAppender but we have the following requirement: If at any time a write to the log fails (due to a full disk, file permissions, etc.) the application must halt immediately, because no logs means no audit data, and that constitutes a high security risk.
> Now, the usual behavior when Logback can't write to the file is to log the error and continue. What would be the right way to handle this?
> Thank you,
> Gabriel
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/listinfo/logback-user

More information about the Logback-user mailing list