tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Tomcat Wiki] Update of "FAQ/Windows" by GianlucaVarisco
Date Wed, 28 Nov 2007 18:53:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tomcat Wiki" for change notification.

The following page has been changed by GianlucaVarisco:

New page:
== Preface ==
The will address various windows issues. Please see the [
Other Resources Link] for more links related to Windows.

== Questions ==

'''Why do I get Out of Environment Space?'''

Check the Tomcat README, and [
this link]

''' When I start up tomcat (or when it is running), I get the error {{{java.lang.IllegalMonitorStateException:
current thread not owner}}}'''

That is weird - but solved.(?) See the [
Tomcat Bug Report] and [
Sun Bug Parade report] for the answer.

'''Can I turn off case sensitivity?'''

[ Yes]

'''Can I use NTLM authentication?'''

With help from the Samba folks, [ it is possible].

'''I want to redeploy web applications, how do I prevent resources from getting locked?'''

Most locking issues will occur with JARs from /WEB-INF/lib, and are useally caused by access
through URLs. Tomcat has mechanisms to allow avoiding locking. In Tomcat 5.0, a mechanism
exists to prevent locking when accessing resources using the getResource method of the URL
classloader (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. 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. 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, b
 ut 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 JSPs without
reloading the application, the changes has to be duplicated to the path where the web application
resources have been copied in the temp folder). 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message