It could also be a virus checker that has a lock on the file, which stops it being renamed?
I think you are on the right track using sysinternals Handle and Filemon, to see which process has a lock on the file at the point the roll it attempted. -- View this message in context: http://logback.10977.n7.nabble.com/logback-RollingFileAppender-problem-on-Windows-Server-2008-Jetty-Shibboleth-IdP-procrun-tp11528p11968.html Sent from the Users mailing list archive at Nabble.com. _______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
