Log4j locking log file in app hot deploy on tomcat
807591Mar 19 2008 — edited Mar 21 2008Hi all,
I'm using a 3rd-party code that uses log4j. The app runs fine, but when I try to redeploy the application, it keeps the log file locked. I'm thinking there's a log4j thread that keeps running somewhere that locks the log file.
I successfully used antiJARLocking="true" in my context.xml to keep tomcat from locking some jar files, and I was trying to use antiResourceLocking="true" (which runs the app in a temp folder, but the log file is still outside the temp folder since it's created by the 3rd-party and it uses a hard coded path. At the end the log file was still locked).
Any ideas on what I can do to not let the file getting locked (or unlocking it for redeploying purposes)?
Thanks,
Andre