From owner-freebsd-java@FreeBSD.ORG Fri May 26 17:30:10 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 8487216A47F for ; Fri, 26 May 2006 17:30:10 +0000 (UTC) (envelope-from vadimnuclight@tpu.ru) Received: from relay1.tpu.ru (relay1.tpu.ru [213.183.112.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DD343D5E for ; Fri, 26 May 2006 17:30:08 +0000 (GMT) (envelope-from vadimnuclight@tpu.ru) Received: by relay1.tpu.ru (Postfix, from userid 501) id 549BB10C96E; Sat, 27 May 2006 00:30:07 +0700 (NOVST) Received: from mail.main.tpu.ru (mail.main.tpu.ru [10.0.0.3]) by relay1.tpu.ru (Postfix) with ESMTP id 3B7FA10C96D; Sat, 27 May 2006 00:30:07 +0700 (NOVST) Received: from mail.tpu.ru ([213.183.112.105]) by mail.main.tpu.ru with Microsoft SMTPSVC(6.0.3790.1830); Sat, 27 May 2006 00:30:06 +0700 Received: from nuclight.avtf.net ([82.117.64.107]) by mail.tpu.ru over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sat, 27 May 2006 00:30:06 +0700 To: "Kurt Miller" , freebsd-java@freebsd.org References: <200605260932.19449.kurt@intricatesoftware.com> <200605261307.06671.kurt@intricatesoftware.com> Message-ID: Date: Sat, 27 May 2006 00:29:01 +0700 From: "Vadim Goncharov" Organization: AVTF TPU Hostel Content-Type: text/plain; format=flowed; delsp=yes; charset=koi8-r MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <200605261307.06671.kurt@intricatesoftware.com> User-Agent: Opera M2/7.54 (Win32, build 3865) X-OriginalArrivalTime: 26 May 2006 17:30:06.0498 (UTC) FILETIME=[079BA020:01C680EA] Cc: 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: Fri, 26 May 2006 17:30:11 -0000 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 ? > 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? -- WBR, Vadim Goncharov