From: markt If true, the Tomcat classloader will take extra measures to avoid
JAR file locking when resources are accessed inside JARs through URLs.
- This will impact startup time of applications, but could prove to be useful
- on platforms or configurations where file locking can occur.
+ This will impact startup time of applications, but could prove to be
+ useful on platforms or configurations where file locking can occur.
If not specified, the default value is false.antiJARLocking is a subset of
+ antiResourceLocking and therefore, to prevent duplicate
+ work and possible issues, only one of these attributes should be set
+ to true at any one time.false.
Please note that setting this to true has some side effects,
- including the disabling of JSP reloading in a running server: see
- Bugzilla 37668.
-
antiJARLocking is a subset of
+ antiResourceLocking and therefore, to prevent duplicate
+ work and possible issues, only one of these attributes should be set
+ to true at any one time.
- Please note that setting this flag to true in applications that are +
Please note that setting this to true has some side
+ effects, including the disabling of JSP reloading in a running server:
+ see
+ Bugzilla 37668.
Please note that setting this flag to true in applications that are
outside the appBase for the Host (the webapps 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.
-