On the Tomcat logs, it reads:
2004-02-27 16:58:55 ApplicationDispatcher[/jsp-apps] Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError
2004-02-27 16:58:55 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
java.lang.OutOfMemoryError
Do you have any idea why this might have happened? Also, how can we avoid such problems in the future?
Asim Alp Educational Networks 55 Broad Street, 10th Floor New York, NY 10004 www.educationalnetworks.net
Tel: +1 (212) 269-0200 Fax: +1 (212) 269-1446 On Feb 27, 2004, at 11:39 AM, Kannan Sundararajan wrote:
Yes, it goes along with subject called Garbage collection and tuning. This
area is a huge, sometimes very quick to tune, and sometimes gives a
nightmare to tune those properties. The nature of this subject grows based
on your application, servers and expectations from user end.
-----Original Message----- From: Asim Alp [mailto:[EMAIL PROTECTED] Sent: Friday, February 27, 2004 11:25 AM To: [EMAIL PROTECTED] Subject: Tomcat heap vs. java.exe
I have a quick question. When I run Tomcat 5.0.18, my java.exe starts with ~65MB. Then as my websites get hits, java.exe starts increasing. I run tomcat with the -Xms128m -Xmx256m options. So the startup heap size of tomcat is 128MB. After my first start, I usually have around 80 MB free memory for Tomcat.
My question is, why is the startup java.exe size is smaller than my total heap size? Does the size of java.exe grow as the heap starts being used. I would expect java.exe to be at least 128 MB (plus the JVM memory) since that is how much is allocated.
Thanks,
Asim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
