From owner-freebsd-java@FreeBSD.ORG  Mon Dec 13 16:08:59 2004
Return-Path: <owner-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 012BA16A505
	for <freebsd-java@freebsd.org>; Mon, 13 Dec 2004 16:08:56 +0000 (GMT)
Received: from turing.morons.org (turing.morons.org [209.237.229.34])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C3B0943D4C
	for <freebsd-java@freebsd.org>; Mon, 13 Dec 2004 16:08:56 +0000 (GMT)
	(envelope-from freebsd@spatula.net)
Received: by turing.morons.org (Postfix, from userid 1001)
	id A69CCA931; Mon, 13 Dec 2004 08:08:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by turing.morons.org (Postfix) with ESMTP
	id 9F8DDA92D; Mon, 13 Dec 2004 08:08:56 -0800 (PST)
Date: Mon, 13 Dec 2004 08:08:56 -0800 (PST)
From: Nick Johnson <freebsd@spatula.net>
X-X-Sender: spatula@turing.morons.org
To: Joris Verschoor <j.verschoor@nefli.nl>
In-Reply-To: <41BDBC4B.40505@nefli.nl>
Message-ID: <20041213080605.U85397@turing.morons.org>
References: <41BDBC4B.40505@nefli.nl>
X-what-happen: someone set up us the bomb
X-Message-Flags: Spatula
Precedence: special-delivery
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-java@freebsd.org
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
List-Id: Porting Java to FreeBSD <freebsd-java.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-java>
List-Post: <mailto:freebsd-java@freebsd.org>
List-Help: <mailto:freebsd-java-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2004 16:08:59 -0000

On Mon, 13 Dec 2004, Joris Verschoor wrote:

> Is there anything I can do to provide more information, for example a
> dump when it's stuck?

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

-- 
"The aptly-named morons.org is an obscenity-laced screed..."
	-- Robert P. Lockwood, Catholic League director of research
Nick Johnson, version 2.1                             http://web.morons.org/