mlkknbr opened a new issue, #259: URL: https://github.com/apache/logging-log4net/issues/259
**Issue Description:** I am encountering the following error in a live production environment that is load balanced across 6 different servers: _**The process cannot access the file 'E:\Sites\ccc\App_Data\Logs\Logs.txt' because it is being used by another process.**_ **Environment Details:** There are 6 servers behind a load balancer. Each server writes logs locally to its own log file at E:\Sites\ccc\App_Data\Logs\Logs.txt. Log4net is configured on each server to write to the local file using the MinimalLock locking model to minimize file locking. Despite this, I occasionally get file locking errors indicating that the log file is being used by another process. **Additional Context:** Since each server writes independently to its own log file, there should be no cross-server file sharing or contention. The error happens intermittently, suggesting a concurrency or file locking issue on the local server. The logging is done using log4net’s rolling file appender with the MinimalLock locking strategy. **Request for Guidance:** Do you have any recommendations or best practices for avoiding such file locking conflicts when using the MinimalLock model in log4net? Could there be configuration adjustments or common pitfalls that might cause this issue despite using MinimalLock? Any advice on how to configure log4net for load balanced multi-server environments to prevent these file access conflicts? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
