From owner-freebsd-java@FreeBSD.ORG Wed Jul 5 19:04:05 2006 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 B1B9916A4E6 for ; Wed, 5 Jul 2006 19:04:05 +0000 (UTC) (envelope-from kurt@intricatesoftware.com) Received: from mta9.srv.hcvlny.cv.net (mta9.srv.hcvlny.cv.net [167.206.4.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CF3A43D53 for ; Wed, 5 Jul 2006 19:04:05 +0000 (GMT) (envelope-from kurt@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta9.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0J1Y00GYQ29MLC00@mta9.srv.hcvlny.cv.net> for freebsd-java@freebsd.org; Wed, 05 Jul 2006 15:03:22 -0400 (EDT) Date: Wed, 05 Jul 2006 15:03:35 -0400 From: Kurt Miller In-reply-to: <1152122995.5382.14.camel@detri015.speed.planet.nl> To: freebsd-java@freebsd.org, martijn@detrics.com Message-id: <200607051503.35873.kurt@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-6 Content-transfer-encoding: 7BIT Content-disposition: inline References: <1152082235.30307.19.camel@detri015.speed.planet.nl> <200607051337.16442.lists@intricatesoftware.com> <1152122995.5382.14.camel@detri015.speed.planet.nl> User-Agent: KMail/1.9.3 Cc: Subject: Re: Apache Tomcat crash on 6.1 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: Wed, 05 Jul 2006 19:04:05 -0000 Hi Martijn, On Wednesday 05 July 2006 2:09 pm, Martijn Veening wrote: > Thanks Kurt, but an out-of-memory error seems unlikely, it's a > SuperMicro server with 1 Gb of memory and 256 Mb dedicated to the JVM > (by JVM startup-options in catalina.sh). Some ideas: 1) check your datasize ulimit for the login class of the user tomcat is running under. 2) set the X malloc() option (ln -s X /etc/malloc.conf) and see if you get a diagnostic message as to why malloc() is returning NULL. 3) watch the java process memory utilization over time with top or ps -l and look for increasing memory usage. > I added the JVM-parameter -XX:+UseMembar now, but i understand that the > diablo-1.5.0_7 has this turned on by default, so that probably doesn't > help Correct > (the server hasn't crashed since though, but is only up for 10 > hours, so not conclusive). > > It is a 2-processor machine though: does that require tuning ? Nothing in particular comes to mind, but you could look through some of Sun's docs at http://java.sun.com/docs/hotspot/index.html Regards, -Kurt