On 29/04/2010 15:01, govind naroji wrote: > 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?
That pretty much sums it up. > 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? You shouldn't see any. > 2) Is it a bad practice to set these attributes to false in a production > environment? No. > 2) Is it true that locking won't occur on a Linux box as frequently as it > can happen on a Windows box? You won't see the issue at all on Linux. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
