From owner-freebsd-java@FreeBSD.ORG Fri May 26 13:32:21 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 B34C816A421 for ; Fri, 26 May 2006 13:32:21 +0000 (UTC) (envelope-from kurt@intricatesoftware.com) Received: from mta7.srv.hcvlny.cv.net (mta7.srv.hcvlny.cv.net [167.206.4.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6559743D46 for ; Fri, 26 May 2006 13:32:21 +0000 (GMT) (envelope-from kurt@intricatesoftware.com) Received: from [172.16.1.72] (ool-457a77e8.dyn.optonline.net [69.122.119.232]) by mta7.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTP id <0IZV0066YK9V5KC0@mta7.srv.hcvlny.cv.net> for freebsd-java@freebsd.org; Fri, 26 May 2006 09:32:20 -0400 (EDT) Date: Fri, 26 May 2006 09:32:19 -0400 From: Kurt Miller In-reply-to: To: freebsd-java@freebsd.org Message-id: <200605260932.19449.kurt@intricatesoftware.com> MIME-version: 1.0 Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7BIT Content-disposition: inline References: <200605251409.13312.lists@intricatesoftware.com> User-Agent: KMail/1.9.1 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 13:32:21 -0000 On Thursday 25 May 2006 2:16 pm, Vadim Goncharov wrote: > 26.05.06 @ 01:09 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. -Kurt