Page History

...

That is weird - but solved. weird issue was observed many years ago and now is a history. See the Tomcat Bug Report #13723 and Sun Bug Parade report #4776385 for the answer.

YesIt is possible in Tomcat 6 and earlier, but not recommended.

...

Most locking issues will occur with JARs from /WEB-INF/lib, and are useally usually caused by access through URLs. Tomcat has mechanisms to allow avoiding locking. In

Since Tomcat 5.0, a mechanism exists to prevent locking when accessing resources using the getResource method of the URL classloader (many URLClassLoader. Many applications, such as Xerces, do not set the use of caching to false before opening the URL connection , causing locking). If such a call occurs, resources inside the JARs will be extracted to the work directory of the web application. to a JAR file, and that causes locking. In Tomcat 5.5, this mechanism is disabled by default (as it has a non negligible influence on startup times, and is often useless), and can be enabled using the antiJARLocking attribute of the Context element. If getResource call occurs, resources inside the JARs will be extracted to the work directory of the web application. There is an alternative to this since Tomcat 6.0.24: you can configure a JreMemoryLeakPreventionListener in your server.xml and it will set the URL connection caching to be off by default.

There is another lock prevention mechanism in Tomcat 5.5 (antiResourceLocking attribute), which will cause the web application files to be copied to the temp folder and run from this location. This has a larger impact on web application startup times, but obviously prevents locking on all resources of the web application. This also allows more flexible management operations as none of the web application resources will be locked, even while the web application is running (as a special note, when making changes to JSPs without reloading the application, the changes has have to be duplicated to the path where the web application resources have been copied in the temp folder).

...

Tomcat uses the Apache Commons Daemon. You can read its documentation at http://commons.apache.org/daemon/procrun.html As a short example, you can create a new Windows Service with the full version number in its name like this:

bin\tomcat6.exe //IS//tomcat6018 tomcat6026 --DisplayName "Apache Tomcat 6.0.18"26"

See also the service.bat file that comes in the *windows<arch>.zip distributives of Tomcat.