From owner-freebsd-java@FreeBSD.ORG Tue May 30 15:07:52 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 0997616A4FC for ; Tue, 30 May 2006 15:07:52 +0000 (UTC) (envelope-from kurt@intricatesoftware.com) Received: from mta3.srv.hcvlny.cv.net (mta3.srv.hcvlny.cv.net [167.206.4.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id AED8943D48 for ; Tue, 30 May 2006 15:07:51 +0000 (GMT) (envelope-from kurt@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta3.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0J03001DT3BUCQ20@mta3.srv.hcvlny.cv.net> for freebsd-java@freebsd.org; Tue, 30 May 2006 11:07:07 -0400 (EDT) Date: Tue, 30 May 2006 11:07:05 -0400 From: Kurt Miller In-reply-to: To: freebsd-java@freebsd.org Message-id: <200605301107.05985.kurt@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7BIT Content-disposition: inline References: <200605261307.06671.kurt@intricatesoftware.com> User-Agent: KMail/1.9.1 Cc: Vadim Goncharov Subject: Re: diablo 1.5 died after 5 day uptime 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: Tue, 30 May 2006 15:07:52 -0000 On Friday 26 May 2006 1:29 pm, Vadim Goncharov wrote: > 27.05.06 @ 00:07 Kurt Miller wrote: > > >> >> From what I can gather from the stack trace, the jvm was > >> > in the process of a graceful shutdown but there wasn't enough > >> > memory for it to pull it off. There is only so much you can > >> > do to protect against out-of-memory errors when you need more > >> > to report it nicely to the user. > >> > >> Hmm, OK. Is there any way to tell Java that memory is about to end > >> before killing ? Or may be a way to make GC to free some memory > >> periodically? May be outside from java, undocumeted external > >> signaling to diablo-jdk ? At last, does it respect login.conf limits > >> at all, doing graceful shutdown before / trying to raise to hard limit ? > >> > > > > If your goal is to limit the amount of memory the jvm uses, > > I would recommend using the standard command line arguments > > that control the heap size (-Xmx & -Xms) and leave your limits > > How can I check default values of these on my system ? Sorry for the delay - holiday weekend here. IIRC, the values are set by the jvm depending on the amount of physical memory in your system. I don't recall how you find out what they are. > > > high. Note that the jvm uses more memory then is controlled > > by the -Xmx arg. You need to leave some head room for that if > > your going to be setting your limits lower. > > OK, thanx. Is that overhead big? It varies depending on what your application does. Overall, I think you will find there is plenty of information on the web about how to tune memory usage of the jvm. -Kurt