Hi,

I am working on a project where we'll be using Tomcat 6.0.20 for Development
and production.

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
http://tomcat.apache.org/tomcat-6.0-doc/config/context.html.
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?

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?

Appreciate your help.

Thank you.
Govind Naroji

Reply via email to