Christian Stöber wrote:
> Now I am using a separate thread pool (executor), which cleans up the
> pool when a thread is idle. And now the memory behavior is almost equal
> to Jetty.
Thanks for posting your analysis. You might be interested to know that
Tomcat 7 will use executors exclusively.
Mar
Tim, thanks for the hint with the BodyContent.
Mark, thanks for your hint to take heap dump.
On this morning the two Tomcat instances were using 200 MB more memory
than the Jetty instances do. So I thought it's a good time to take a heap
dump.
In the heap histogram in jhat I saw a big differe
If you use JSP tags where the JSP body does not directly stream but
needs buffered for the tag to finish processing it (using BodyContent) -
then tomcat will allocate and reuse these. If you are creating pages
with large body contents - this can take *A LOT* of memory. The rational
is to reuse
Christian Stöber wrote:
> Hello list,
>
> we are about to migrate our webserver cluster from Jetty 5.1.14 to
> Tomcat 6.0.20. Currently there are four servers in our cluster with
> simple load balancing and no session clustering.
>
> At the moment we are testing Tomcat on 2 nodes of our cluster (
Hello list,
we are about to migrate our webserver cluster from Jetty 5.1.14 to
Tomcat 6.0.20. Currently there are four servers in our cluster with
simple load balancing and no session clustering.
At the moment we are testing Tomcat on 2 nodes of our cluster (also no
session clustering yet).
