tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6007] - JSP-servlet cache is not deleted
Date Thu, 24 Jan 2002 23:22:12 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6007>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6007

JSP-servlet cache is not deleted





------- Additional Comments From ana.von.klopp@sun.com  2002-01-24 23:22 -------
Remy, I think your assessment is correct, but it's about situations where the
Tomcat server is used as a deployment environment. Damian is describing 
a situation where a developer is using the Tomcat server as a test running tool.
Those users will treat the server differently. 

It's pretty normal to switch from executing one module to executing another in
that scenario (with both modules declared to be the root context). We allow
users to deploy multiple modules at a time, but it's usually going to be quicker
to run first one and then the other. 

I understand and agree with your concerns about making the server slower.
Ideally, we'd like it if the server used a different cache, but that sounds like
it would be considerable extra work for the tomcat development team. Would it be
possible to add a flag to the server which permits the behaviour that you 
described in (b) above when the server is used during development, as opposed to
when it is running? 

b) Erase all generated classes and servlets when shutting down. 

You're correct about the consequences: 

"This is very bad also, since it voids the benefits of precompilation,
and would create permanent memory leaks (as javac leaks memory each
time a class is compiled) and bad performance."

but in the development scenario, those JSPs need to be recompiled
anyway! We don't want to force the behaviour on the server at all
times, we simply want it as a possibility when the server is used for
development purposes. 

Would be grateful if you could assess whether you'd reconsider if this issue
could be resolved. It would make a big difference to my team.

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


Mime
View raw message