David Rees wrote:
On 3/7/06, Yaroslav Sokolov <[EMAIL PROTECTED]> wrote:
Ok, I can make the next conclusions:
1. Tomcat eats resources on first opening of any jsp page and never returns
them back - servlets just are never unloaded.
2. As it happens in all the versions of Tomcat, there are many jsps, not
meeting requirements
of the specification (no destroy() method when there is some useful data in
fields) but well working under Tomcat.
3. We do not want to change this situation ( -> I shall not even try to send
any better patch here :-\ (but I will ;-) ) )
What about my previous suggestion of externalizing JSP strings, but
only externalizing strings greater than a certain (user configurable)
size? That would give you huge memory savings in your test case
(running static .html files as JSPs) while allowing users to retain
the existing functionality without a performance hit.
I already have this extension. I initiated this topic to see the community
opinion about situation when JSPs were forever in memory after first loading.
I have seen the opinion.
-Dave
Regards,
Yarick.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
