tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Nybro Bolding" <thomas.bold...@danskebank.dk>
Subject Vedr.: Garbage Collection issues
Date Mon, 01 Dec 2003 07:09:11 GMT
Without knowing your system setup especially JDK version, RAM and # of 
processors my guess is that it could be due to an undersized heap and a 
high call-setup rate.
If the pressure on the old collector is heavy enough, it can force the old 
collector to revert to the traditional mark-sweep collector. If the old 
collector is still unable to keep up, the system can begin to thrash, and 
finally, throw an out-of-memory exception.
Start Tomcat with verbose/xloggc to profile your applications.

/Thomas






"Neal" <nealcabage@yahoo.com>
01-12-03 02:21
Besvar venligst til "Tomcat Users List"

 
        Til:    "'Tomcat Users List'" <tomcat-user@jakarta.apache.org>
        cc: 
        Vedr.:  Garbage Collection issues

My Tomcat 4.1 (hosted on Linux) seems to have a problem in recent months
with crashing due to unavailable free RAM.  Specifically I get a
java.error.outOfMemory exception.  If check the RAM available
(Runtime.getRuntime().totalMemory()), I can see it ticking down through
the week.  If explicitly run garbage collection however my RAM totally
frees up and all is well (Runtime.getRuntime().gc();).

Why would this happen?  Surely this isn't due to a programming error on
my part, otherwise, the resources should automatically released whenever
the JRE performs periodic garbage collection. Isn't that correct?
Anyone have any theories as to what this may mean and what the best
solution would be?

Thanks.
Neal



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org





<FONT SIZE=1 FACE="Arial">_______________
Vi goer opmaerksom paa, at denne e-mail kan indeholde fortrolig information. Hvis du ved en
fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge
svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller
kopiere den.
Selv om e-mailen og ethvert vedhaeftet bilag efter vores overbevisning er fri for virus og
andre fejl, som kan paavirke computeren eller it-systemet, hvori den modtages og laeses, aabnes
den paa modtagerens eget ansvar. Vi paatager os ikke noget ansvar for tab og skade, som er
opstaaet i forbindelse med at modtage og bruge e-mailen.
_______________
Please note that this message may contain confidential information. If you have received this
message by mistake, please inform the sender of the mistake by sending a reply, then delete
the message from your system without making, distributing or retaining any copies of it.
Although we believe that the message and any attachments are free from viruses and other errors
that might affect the computer or IT system where it is received and read, the recipient opens
the message at his or her own risk. We assume no responsibility for any loss or damage arising
from the receipt or use of this message.
</FONT>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message