From owner-freebsd-java@FreeBSD.ORG Fri May 26 15:41:51 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 CAC8C16A531 for ; Fri, 26 May 2006 15:41:51 +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 1FC4343D53 for ; Fri, 26 May 2006 15:41:06 +0000 (GMT) (envelope-from vadimnuclight@tpu.ru) Received: by relay1.tpu.ru (Postfix, from userid 501) id 760C010C91B; Fri, 26 May 2006 22:41:03 +0700 (NOVST) Received: from mail.main.tpu.ru (mail.main.tpu.ru [10.0.0.3]) by relay1.tpu.ru (Postfix) with ESMTP id 5CEA810C903; Fri, 26 May 2006 22:41:03 +0700 (NOVST) Received: from mail.tpu.ru ([213.183.112.105]) by mail.main.tpu.ru with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 May 2006 22:41:03 +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); Fri, 26 May 2006 22:41:02 +0700 To: "Kurt Miller" References: <200605251409.13312.lists@intricatesoftware.com> <200605260932.19449.kurt@intricatesoftware.com> Message-ID: Date: Fri, 26 May 2006 22:39:57 +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: <200605260932.19449.kurt@intricatesoftware.com> User-Agent: Opera M2/7.54 (Win32, build 3865) X-OriginalArrivalTime: 26 May 2006 15:41:02.0780 (UTC) FILETIME=[CB3F7FC0:01C680DA] Cc: freebsd-java@freebsd.org 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 15:41:55 -0000 26.05.06 @ 20:32 Kurt Miller wrote: >> >> I have an SMP (HTT) machine with 5.5-PRERELEASE, using official >> >> diablo 1.5 jdk >> >> binaries from beginning of April. As suggested, I now run java with >> >> -XX:+UseMembar cmdline switch, that resolved problem with crashing >> >> application after startup. >> >> But today after 5 days uptime now-debugged-and-set-to-long-run server >> >> process >> >> have crashed, with 100M coredump file. What happened? Below are log >> and >> >> gdb backtrace. >> >> As some additional info: I have limits in login.conf, 32M for >> resident >> >> size >> >> and 256M for virtual mem size; yesterday when I looked at process >> stats >> >> it was about 10M resident and 250M virtual - could be a reason?.. >> > >> > Hi, >> > >> > It does appear that you've run out of vm. >> > >> > >> >> #21 0x0a3fceda in vm_exit_out_of_memory () >> >> from /usr/local/diablo-jdk1.5.0/jre/lib/i386/client/libjvm.so >> >> But so why it dies on signal 11 with scary logs and coredump, instead of >> descriptive out-of-memory diagnostics and graceful shutdown? Isn't that >> a bug ? > >> 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 ? -- WBR, Vadim Goncharov