title: Tomcat 6 | What's the significance of antiResourceLocking & antiJARLocking?
body: <p>I am working on a project where we'll be using Tomcat 6.0.20 for Development and production.</p>
  
  <p>I came across some issues related to hot deployment which requires one to set Context.antiResourceLocking to false in server.xml. I had some questions on antiResourceLocking and antiJARLocking.
  I have gone through the reference at <a href="http://tomcat.apache.org/tomcat-6.0-doc/config/context.html" rel="noreferrer">http://tomcat.apache.org/tomcat-6.0-doc/config/context.html</a>.</p>
  
  <p>What I can't understand is what exactly do you mean by a JAR getting locked or a resource getting locked. What I have read so far is that the locking problem usually comes when you are undeploying an application which fails due to a process having a lock on the file/jar. Can someone please point me to anything where I can read more on this issue?</p>
  
  <p>My questions are:
  1) If I set antiJARLocking and/or antiResourceLocking to false what are the problems that I can get? Can some one please provide an example?
  2) Is it a bad practice to set these attributes to false in a production environment?
  2) Is it true that locking won't occur on a Linux box as frequently as it can happen on a Windows box?</p>
  
  <p>Appreciate your help.</p>
  
  <p>Thank you.</p>
  
  <p>Govind N.</p>