Tomcat配置context.xml问题

关于Tomcat的配置文件问题，请参考Apache Tomcat官网Document菜单，根据版本号选择恰当的Reference。

我使用的环境：netbeans 内嵌 Tomcat 8.0

(1)<context> 标签内配置的参数antiResourceLocking和reloadable

<A>antiResourceLocking

官网原文：

If true, Tomcat will prevent any file locking. This will significantly impact startup time of applications, but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur. If not specified, the default value is false.

Please note that setting this to true has some side effects, including the disabling of JSP reloading in a running server: seeBugzilla 37668.

Please note that setting this flag to true in applications that are outside the appBase for the Host (thewebapps directory by default) will cause the application to be deleted on Tomcat shutdown. You probably don't want to do this, so think twice before setting antiResourceLocking=true on a webapp that's outside the appBase for its Host.

文中提示说该属性对热部署有好处，可以防止文件锁定（具体文件锁定有什么用还没搞清楚），但是，影响程序的启动时间（还有其他副作用，在此显次要）。所以Tomcat起初的设定就是false。试了试，将该属性设为true时，netbeans启动项目就花很长时间，服务器上也报错。总之实践证明它不友好。

<B>reloadable

官网原文：

Set to true if you want Catalina to monitor classes in/WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications. That's why the default setting for this attribute isfalse. You can use the Manager web application, however, to trigger reloads of deployed applications on demand.

该属性则是实时监测编译后的class文件和lib下引用的jar包的，为true则无需重启web app。若为false则需要你重新部署。缺点就是需要大量的运行时开销，也是想当占用时间的，搞不好，服务器死那了，就呵呵了。它一样不是很友好。