I am looking at the failures that are occurring in the RollingAppenderSizeTest in the Jenkins build. I am working at modifying the code so that the asynchronous tasks will complete before shutdown is allowed to complete. But I am running into an issue I am not sure how to resolve. The test is configured to have the log file roll over after 500 bytes have been written. It seems that some of the compression algorithms take longer than it takes to write 500 bytes, so after the maximum number of files are reached the system is rolling over on top of files that are in the process of being archived, so we get rename/move and delete problems.
Any ideas? Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
