Hello again Zach,
As the documentation notes, antiResourceLocking will prevent JSP reloading
on a running server. If jar locking is your only problem, you should be able
to just use antiJARLocking.
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
-Brian O'Rourke
On 1/9/06,
e Tomcat will keep a hold on
> the jars that are in the WEB-INF/lib directory slowing down my
> development.
Two options you may want to look into are "antiJARLocking" and
"antiResourceLocking", both of which can be specified at the context level.
http://tomcat.apache.org
Hello,
I'm trying to find out the number of requests currently being processed by
my Tomcat server using JMX. I am using Tomcat 5.5.12, where it is no longer
possible to find this out by counting the RequestProcessor beans returned by
a JMX query - I'm told this is because of a new feature (
http:
that the context
name is determined by the name of the war file. Is there a working set of
functionality that FarmWarDeployer handles now, or should I just stay away
from it altogether?
Thanks,
Brian O'Rourke
