From owner-freebsd-java@FreeBSD.ORG Wed Jul 5 21:28:06 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 51DA616A4DE for ; Wed, 5 Jul 2006 21:28:06 +0000 (UTC) (envelope-from martijn@detrics.com) Received: from psmtp04.wxs.nl (psmtp04.wxs.nl [195.121.247.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5EA843D45 for ; Wed, 5 Jul 2006 21:28:05 +0000 (GMT) (envelope-from martijn@detrics.com) Received: from [10.0.0.150] (ip503d6288.speed.planet.nl [80.61.98.136]) by psmtp04.wxs.nl (iPlanet Messaging Server 5.2 HotFix 2.07 (built Jun 24 2005)) with ESMTP id <0J1Y002HQ8YRTD@psmtp04.wxs.nl> for freebsd-java@freebsd.org; Wed, 05 Jul 2006 23:28:03 +0200 (MEST) Date: Wed, 05 Jul 2006 23:28:04 +0200 From: Martijn Veening In-reply-to: <200607051503.35873.kurt@intricatesoftware.com> To: Kurt Miller , freebsd-java@freebsd.org Message-id: <1152134883.7788.12.camel@detri015.speed.planet.nl> Organization: Detrics MIME-version: 1.0 X-Mailer: Ximian Evolution 1.4.6 References: <1152082235.30307.19.camel@detri015.speed.planet.nl> <200607051337.16442.lists@intricatesoftware.com> <1152122995.5382.14.camel@detri015.speed.planet.nl> <200607051503.35873.kurt@intricatesoftware.com> Content-Type: text/plain Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Apache Tomcat crash on 6.1 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: martijn@detrics.com List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jul 2006 21:28:06 -0000 Hi Kurt, thnx for suggestions, Indeed it seems that java process memory increases, although the reading is different from the tomcat manager reading. The size started at 450M (res 100M) and after 6 hours increased to 600M (res 160M). I can imagine that if that continues another 10 hours, the 1 Gb limit is reached causing crash. Tomcat however read lower memory-usage, but that will be memory within the JVM-reserved memory, which differs from the process-memory in FreeBSD (I presume). Could it be a memory leak ? Or is this increase normal because it contains cached memory which can be freed when nescessary ? And where could I see the diagnostic message for the malloc() function ? Martijn Veening www.detrics.com On Wed, 2006-07-05 at 21:03, Kurt Miller wrote: > 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 > _______________________________________________ > 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" >