Why are you explicitly setting the min/max heap sizes so small (i.e., -Xms8m, -Xmx64m)? Given you have so much RAM on your server, I'd think you'd want to allocate a heap size on the order of *100s* of Megs (e.g., -Xms200m -Xmx400m), not merely 8-64. Thoughts? -jwh -----Original Message----- From: Thomas S [mailto:[EMAIL PROTECTED]] Sent: Monday, June 18, 2001 11:05 PM To: [EMAIL PROTECTED] Subject: Help!! "Tomcat-3.2.2 Out of Memory Error" Hello, Please help me!!!! Config:- Apache-1.3.14 +Tomcat 3.2.2 with mod_jk and Sun JDK 1.3 in RH-Linux 7.0 I am getting out of memory error in the tomcat tc logs. Tomcat servers servlets and jsp with jdbc connections. This problem seems to be periodic after 12-13 hrs of tomcat restart. We are using Dell Webapps server with 1G memory installed. I could notice a free memory of ~200MB when tomcat spits this error. I have gone through the tomcat mailing list, tried setting -Xms8m -Xmx64m as tomcat options, but vain. After this error, tomcat is not able to serve any sevlets, and not able to controle the jdbc connection, hence the jdbc connection goes out of control , results spawning n. no of connections to database. Is this a caching over flow problem? or JVM problem? Thanks in Advance Thomas Systems Engineer Error: --------------- 2001-06-19 08:11:53 - Ctx( /xxx ): Exception in: R( /xxx + /servlet/xxx + null) - java.lang.OutOfMemoryError <<no stack trace available>> 2001-06-19 08:14:20 - Ctx( /xxx ): Exception in: R( /xxx+ /servlet/xxx + null) - java.lang.OutOfMemoryError <<no stack trace available>> 2001-06-19 08:15:55 - Ctx( /xx ): Exception in: R( /xx + /servlets/xxx + null) - java.lang.OutOfMemoryError <<no stack trace available>> ----------------------------------
