From owner-freebsd-java@FreeBSD.ORG Sat Jul 30 20:32:25 2005 Return-Path: X-Original-To: freebsd-java@freebsd.org Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32ADB16A41F for ; Sat, 30 Jul 2005 20:32:25 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) Received: from Deliverance.voxify.com (65-123-2-7.dia.cust.qwest.net [65.123.2.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1AE843D48 for ; Sat, 30 Jul 2005 20:32:24 +0000 (GMT) (envelope-from Robert.Faulds@voxify.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 30 Jul 2005 13:32:24 -0700 Message-ID: <331CA3AB8A236A488C92DEC289C7D04DD95D80@Deliverance.voxify.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: JVM crashes Thread-Index: AcWTijAQGkK9N/H3QhSGeYVyEARTPgAJnTUgAGVFsiA= From: "Robert Faulds" To: Subject: RE: JVM crashes X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jul 2005 20:32:25 -0000 I had some very similar crashes that turned out to be too small default permanent generation size. Starting tomcat with a fixed heap and bumping up the permsize solved them for me. Bumping the heap alone was not enough. -server -XX:+UseParNewGC -XX:PermSize=3D128m -XX:MaxPermSize=3D128M = -Xms700M -Xmx700M These tools have proven invaluable in diagnosing OOM's. http://java.sun.com/performance/jvmstat/ and for the JDK 5.0 phobic http://java.sun.com/performance/jvmstat/faq.html#11 -----Original Message----- From: owner-freebsd-java@freebsd.org [mailto:owner-freebsd-java@freebsd.org] On Behalf Of Christopher Farley Sent: Thursday, July 28, 2005 7:16 AM To: freebsd-java@freebsd.org Subject: JVM crashes I'm running jdk-1.4.2p6_3.=20 One of my programs is causing the JVM to crash with the following error: Exception in thread "CompilerThread1" java.lang.OutOfMemoryError: requested 32760 bytes for ChunkPool::allocate. Out of swap space? A search of google brings up loads of problems related to Tomcat, but this program has nothing to do with Tomcat. To my knowledge, none of the libraries I am using use JNI code at all.=20 First, is there anything programming error that could cause this crash? I need to know if I should be scrutinizing my code for memory leaks, etc. I have run the program through a memory profiler, but not the production system... Everything looks okay. Second, would it be worth installing the latest jvm patchset to see if this fixes the problem?=20 Finally, if one of my libraries is causing this to happen, how would I go about determining the cause? One final, probably irrelevant detail -- the jvm will usually crash within the first couple of hours of being launched. If it survives more than a few hours, it seems to go on forever with no problems. I haven't seen any other pattern in the crashes! Thanks for any help you can provide! --=20 Christopher Farley www.northernbrewer.com _______________________________________________ freebsd-java@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-java To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org"