On Mon, 22 Nov 2004 16:37:39 +0200, Carl Olivier [EMAIL PROTECTED] wrote:
Ooppps.
Sorry -meant 300 seconds!
I think this could be improved, but the penalty will stay significant.
antiJARLocking prevents locking through usage of getResource on the
classloader (where you get a URL to an entry
which a class not found exception was
thrown! I checked the new JAR using different tools and it is fine!
Thanks,
Carl
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 23, 2004 1:08 PM
To: Tomcat Users List
Subject: Re: Tomcat 5.5.4 - classes
Hi,
Thanks - yes I realise. Wonderin why tihs has been done? Was the old
classloader mechanisms in 5.0.x that broken? Not criticising, just
trying
to understand the reasoning here.
No, it was fine: the problems arose due to OS behavior mostly,
specifically Windoze, and how virtual file
: Tomcat 5.5.4 - classes in classpath not being released
Greetings.
Having the following problem using Tomcat 5.5.4 under JDK 1.5:
After running my webapp for a bit in a development environment, I want to
copy new and replacement classes to the webapp classes location, but
sometimes (about 50/50) I
: Monday, November 22, 2004 3:45 AM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hi.
Further to my email below, I have noticed that it happens after the
first
time I re-deoply classes - i.e. after the first context reload...
Carl
-Original Message
Ok, thanks!!
Appreciate the response as always!
Carl
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Monday, November 22, 2004 3:58 PM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hi,
You would need to turn
Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hi,
You would need to turn on the antiJARLocking or antiResourceLocking features
of Tomcat 5.5.x (they are Context attributes, use either one but not both at
the same time).
Yoav Shapira http://www.yoavshapira.com
PROTECTED]
Sent: Monday, November 22, 2004 9:37 AM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hectic.
When it says startup performance penalties its not kidding eh? Context
set
tot antiResourceLocking=true and added like 30 seconds to the server
startup
, 2004 4:45 PM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hi,
Yup, not kidding. However, the reason to turn this on is to do in-place
reloading, as opposed to server restarting, so the penalty is easily
amortized over a few (not many) reloads.
Yoav
Ooppps.
Sorry -meant 300 seconds!
-Original Message-
From: Carl Olivier [mailto:[EMAIL PROTECTED]
Sent: Monday, November 22, 2004 4:37 PM
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4 - classes in classpath not being released
Hectic.
When it says startup performance penalties its
Hi,
(e.g. get the StandardHost and call remove on the service/engine and
then
recreate a StandardHost instance with all the relevant settings, then
calling deploy and start on it...)
This is really not a recommended practice. With the increased JMX and
Logging interaction, it's hard to get
Greetings.
Having the following problem using Tomcat 5.5.4 under JDK 1.5:
After running my webapp for a bit in a development environment, I want to
copy new and replacement classes to the webapp classes location, but
sometimes (about 50/50) I cannot overrite/delete some of the classes - as
the
12 matches
Mail list logo
