Hi,
I have found, that once loaded jsp-servlets are never unloaded.
To test I just configured tomcat to process *.html files by JspServlet
and then traversed jdk documentation. The result was not very exciting -
after browsing ~ 150 pages tomcat cried "java.lang.OutOfMemoryError: Java heap
spac
you think your OOME has to do with the number of JspServlet
instances? Run a profiler, you might be surprised.
Yoav
On 3/3/06, Yaroslav Sokolov <[EMAIL PROTECTED]> wrote:
Hi,
I have found, that once loaded jsp-servlets are never unloaded.
To test I just configured tomcat to process *.h
ld.
Costin
On 3/3/06, Yaroslav Sokolov <[EMAIL PROTECTED]> wrote:
Hi,
I have found, that once loaded jsp-servlets are never unloaded.
To test I just configured tomcat to process *.html files by JspServlet
and then traversed jdk documentation. The result was not very exciting -
afte
course,
such a
policy should be optional.
Implementation of such a policy, as I already have written, is more complex
patch than
the illustration: "as internal structure containing jsp-servlets, it seems,
was not designed for
such actions..."
--
Regards,
Yaroslav Sokolov.
own of the web application.
So it might break a lot of code.
>
>
>
> Costin
>
[skipped]
--
Regards,
Yaroslav Sokolov.
the background compilation thread, and now this).
>
> Rémy
>
--
Regards,
Yaroslav Sokolov.
debug
> problems.
>
> By 'spec compliance' I mean more 'compatibility with the existing spec
> _and_ the current usage of the spec'. The later is IMO more important
> in many cases than the letter or any interpretation of the spec.
>
> Costin
>
> On 3/6/06,
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 ar
