David Rees wrote:
All increasing the -Xmx256M setting will do is delay the onset of the OOM condition, it won't fix it. If you compile a lot of JSPs, make sure that in the container's web.xml you set the fork attribute of the JspServlet to true or use jikes, otherwise that will leak memory as well.
With a machine that has 500M, I wouldn't use more than 256M for Tomcat unless nothing else is running on it.
-Dave
Sorry but how do I "set the fork attribute of the JspServlet to true"?
This seems like an obvoius memory leak in somewhere IMHO:
I run tomcat-4.1.29 SUN JDK 1.4.1 (or 1.4.2 if that matters) and creating this test.jsp
<html><head></head><body>
<%
System.gc();
out.print(Runtime.getRuntime().freeMemory());
out.print("\t" + Runtime.getRuntime().totalMemory());
out.print("\t" + new java.util.Date());
%>
</body></html>
and following bash script:
while [ 1 ]
do
/usr/bin/lynx -dump http://localhost:8080/test.jsp >> /tmp/m.txt
touch /usr/local/jakarta-tomcat-4.1.29/webapps/ROOT/test.jsp
done
slowly crashes the tomcat instance. You can watch the progress via "tail -f /tmp/m.txt".
Is this how is tomcat supposed to work (on SUN's JDK)?
Best regards,
David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
