From owner-freebsd-java@FreeBSD.ORG Mon Dec 13 16:39:55 2004 Return-Path: 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 66B8A16A4CE for ; Mon, 13 Dec 2004 16:39:55 +0000 (GMT) Received: from gollum.cambrium.nl (mx1.cambrium.nl [217.19.16.130]) by mx1.FreeBSD.org (Postfix) with SMTP id 97D3143D2D for ; Mon, 13 Dec 2004 16:39:54 +0000 (GMT) (envelope-from j.verschoor@nefli.nl) Received: (qmail 23489 invoked from network); 13 Dec 2004 16:39:53 -0000 Received: from 217-19-20-68.dsl.cambrium.nl (HELO ?192.168.1.142?) (217.19.20.68) by gollum.cambrium.nl with SMTP; 13 Dec 2004 16:39:53 -0000 Message-ID: <41BDC5E7.7030509@nefli.nl> Date: Mon, 13 Dec 2004 17:40:07 +0100 From: Joris Verschoor Organization: Nefli B.V. User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-java@freebsd.org References: <41BDBC4B.40505@nefli.nl> <20041213080605.U85397@turing.morons.org> In-Reply-To: <20041213080605.U85397@turing.morons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 5.3-RELEASE + JDK1.4 native in a Jail -> hangs 99% cpu on kserel X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 16:39:55 -0000 Nick Johnson wrote: >kill -3 on the Java process should cause it to do a thread/stack dump, >which may prove useful. > > >Another thing you can try is running java with -Xrunhprof:depth=8, though >note that this will have a significant impact to performance. It will, >however, produce stack traces (of depth 8 in this case) for each thread >when you kill the JVM normally (not with kill -9). > > Nick > > > Ok.. I just tried it when it was still running (I assume -3 will have the same effect as ctrl-break in java/win32) After that I saw the process go into kserel and the cpu time rose to 99% again. There was no stacktrace anywhere (stderr / stdout) So I killed it, and started it again. When it started, I got the Resource temporarily unavailable error I tried to do a normal shutdown (killall java) The same thing happened.. so that's very strange.. if I run /usr/local/etc/rc/.d/resin3.sh stop, and it was not in the kserel loop, it will stop normally