Hi, We recently upgraded our Log4Net package from 1.2.13 to 2.0.14 to remediate a security flaw found in the old package. After upgrading we have found an issue that is not allowing 2 instances of an application to write to the same file location. We have a blue/green pool deployment strategy where each server has an active and inactive application instance and on the first deployment we see that the active version logs as expected, but after swapping the pools the new active application is unable to log as the now inactive application seems to have a lock on the file.
We were able to make it work with 2.0.3, but 2.0.10 is the oldest version that does not have the flaw. Any versions of the library without the flaw has this locking issue. Can you help us to raise an issue to be taken up for development in future releases? Thanks, Kevin Gardenhire Charles Schwab & Co. | Enterprise Middleware and Online Security Technology (EMOST) Classification: Schwab Internal
