Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Sat, 27 Mar 2010 21:22:51 -0000
Message-ID: <20100327212251.9971.52410@eos.apache.org>
Subject: 
 =?utf-8?q?=5BTomcat_Wiki=5D_Update_of_=22FAQ/Windows=22_by_KonstantinKoli?=
 =?utf-8?q?nko?=

Dear Wiki user,

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

The "FAQ/Windows" page has been changed by KonstantinKolinko.
The comment on this change is: Updated.
http://wiki.apache.org/tomcat/FAQ/Windows?action=3Ddiff&rev1=3D6&rev2=3D7

--------------------------------------------------

  =

  <<Anchor(Q2)>>'''When I start up tomcat (or when it is running), I get th=
e error {{{java.lang.IllegalMonitorStateException: current thread not owner=
}}}'''
  =

- That is weird - but solved.(?) See the [[http://issues.apache.org/bugzill=
a/show_bug.cgi?id=3D13723|Tomcat Bug Report]] and [[http://developer.java.s=
un.com/developer/bugParade/bugs/4776385.html|Sun Bug Parade report]] for th=
e answer.
+ That weird issue was observed many years ago and now is a history. See th=
e [[http://issues.apache.org/bugzilla/show_bug.cgi?id=3D13723|Tomcat Bug Re=
port #13723]] and [[http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=3D47=
76385|Sun Bug Parade report #4776385]] for the answer.
  =

  <<Anchor(Q3)>>'''Can I turn off case sensitivity?'''
  =

- [[http://tomcat.apache.org/tomcat-4.1-doc/config/resources.html|Yes]]
+ It is [[http://tomcat.apache.org/tomcat-6.0-doc/config/context.html|possi=
ble]] in Tomcat 6 and earlier, but not recommended.
  =

  <<Anchor(Q4)>>'''Can I use NTLM authentication?'''
  =

@@ -34, +34 @@

  =

  <<Anchor(Q5)>>'''I want to redeploy web applications, how do I prevent re=
sources from getting locked?'''
  =

- Most locking issues will occur with JARs from /WEB-INF/lib, and are useal=
ly caused by access through URLs. Tomcat has mechanisms to allow avoiding l=
ocking. In Tomcat 5.0, a mechanism exists to prevent locking when accessing=
 resources using the getResource method of the URL classloader (many applic=
ations, such as Xerces, do not set the use of caching to false before openi=
ng the URL connection, causing locking). If such a call occurs, resources i=
nside the JARs will be extracted to the work directory of the web applicati=
on. In Tomcat 5.5, this mechanism is disabled by default (as it has a non n=
egligible influence on startup times, and is often useless), and can be ena=
bled using the antiJARLocking attribute of the Context element. There is an=
other lock prevention mechanism in Tomcat 5.5 (antiResourceLocking attribut=
e), which will cause the web application files to be copied to the temp fol=
der 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 o=
f the web application resources will be locked, even while the web applicat=
ion is running (as a special note, when making changes JSPs without reloadi=
ng the application, the changes has to be duplicated to the path where the =
web application resources have been copied in the temp folder). =

+ Most locking issues will occur with JARs from /WEB-INF/lib, and are usual=
ly caused by access through URLs. Tomcat has mechanisms to allow avoiding l=
ocking.
+ =

+ Since Tomcat 5.0, a mechanism exists to prevent locking when accessing re=
sources using the getResource method of the URLClassLoader. Many applicatio=
ns, such as Xerces, do not set the use of caching to false before opening t=
he URL connection to a JAR file, and that causes locking. In Tomcat 5.5, th=
is mechanism is disabled by default (as it has a non negligible influence o=
n startup times, and is often useless), and can be enabled using the `antiJ=
ARLocking` attribute of the [[http://tomcat.apache.org/tomcat-6.0-doc/confi=
g/context.html|Context]] element. If getResource call occurs, resources ins=
ide 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 =
[[http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/core/JreM=
emoryLeakPreventionListener.html|JreMemoryLeakPreventionListener]] in your =
`server.xml` and it will set the URL connection caching to be off by defaul=
t.
+ =

+ There is another lock prevention mechanism in Tomcat 5.5 (`antiResourceLo=
cking` 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 resour=
ces of the web application. This also allows more flexible management opera=
tions as none of the web application resources will be locked, even while t=
he web application is running (as a special note, when making changes to JS=
Ps without reloading the application, the changes have to be duplicated to =
the path where the web application resources have been copied in the temp f=
older). =

  =

  <<Anchor(Q6)>>'''Can I use UNC paths?'''
  =

@@ -56, +60 @@

  =

  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 --DisplayName "Apache Tomcat 6.0.18"}=
}}
+ {{{bin\tomcat6.exe //IS//tomcat6026 --DisplayName "Apache Tomcat 6.0.26"}=
}}
  =

+ See also the `service.bat` file that comes in the `*-windows-<arch>.zip` =
distributives of Tomcat.
+=20

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org