hello!

i'm evaluating the same application (apache-struts- & vm- based) on tomcat

 4.1.30 & 5.0.19

1) using jmeter to create about 1000 sessions
2) waiting until all sessions have timed out (manager-appl. says 0 sessions)
3) repeating these steps a few times (say 10 times)

on 5.0.19:
depending on the configured jvm-mx-heap size this results ealier or later in
an OutOfMemoryException.

on 4.1.30:
exactly the same application deployed, does not show that behavior.

any ideas? i'm not storing anything in the session-ctx, nor having any
servlets using static variables (that might grow). -> however, this would
lead into a memory leak on 4.1.30 as well.

from my point of view there is no reason for the application not to memory leak
on 4.1.30 but on 5.0.19?

regards

christoph loibl

--
CHRISTOPH LOIBL >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
mailto:c@(protected)
http://pix.tix.at  |          is your Windows box."
CHL-RIPE >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PGP-Key-ID: 0x4B2C0055 >>>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)