Any idea why JVM would run out of memory? I thought GC would clean up the memory at a certain ratio.
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 5:27 PM, [EMAIL PROTECTED] wrote:
oops! kill -3 <process_id_of_Tomcat>
RS
[EMAIL PROTECTED]
tric.com To: "Tomcat Users List"
<[EMAIL PROTECTED]>
02/27/2004 04:26 cc:
PM Subject: Re: Tomcat heap vs. java.exe
Please respond to
"Tomcat Users
List"
kill -a <process_id_of_Tomcat>
Thanks, RS
Asim Alp
<[EMAIL PROTECTED] To: "Tomcat Users List" tworks.net> <[EMAIL PROTECTED]> cc:
02/27/2004 04:21 PM Subject: Re: Tomcat
heap vs. java.exe
Please respond to
"Tomcat Users List"
How can I take a thread dump?
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 5:16 PM, [EMAIL PROTECTED] wrote:
OutOfMemory errors sometimes show up when the java vm runs low on memory. Since you have increased the heap size, could you take a thread dump to see if there are any CPU burning threads or any threads waiting on a resource?
Thanks, RS
Asim Alp <[EMAIL PROTECTED] To: "Tomcat Users List" tworks.net> <[EMAIL PROTECTED]> cc: 02/27/2004 04:14 PM Subject: Re: Tomcat heap vs. java.exe Please respond to "Tomcat Users List"
Our sites have just went down for a couple of minutes. I solved the problem by restarting Tomcat. At the time of the crash, java.exe was about 345MB. I'm running tomcat with the -Xms128m -Xmx256m options. Our server has 1GB physical ram.
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]
This transmission is intended to be strictly confidential. If you are
not
the intended recipient of this message, you may not disclose, print,
copy
or disseminate this information. If you have received this in error,
please
reply and notify the sender (only) and delete the message. Unauthorized
interception of this e-mail is a violation of federal criminal law.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This transmission is intended to be strictly confidential. If you are not
the intended recipient of this message, you may not disclose, print, copy
or disseminate this information. If you have received this in error, please
reply and notify the sender (only) and delete the message. Unauthorized
interception of this e-mail is a violation of federal criminal law.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This transmission is intended to be strictly confidential. If you are not
the intended recipient of this message, you may not disclose, print, copy
or disseminate this information. If you have received this in error, please
reply and notify the sender (only) and delete the message. Unauthorized
interception of this e-mail is a violation of federal criminal law.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
