From owner-freebsd-java@FreeBSD.ORG Mon Apr 28 14:41:37 2003 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 EB60F37B401 for ; Mon, 28 Apr 2003 14:41:37 -0700 (PDT) Received: from chen.org.nz (chen.org.nz [210.54.19.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id A294C43FB1 for ; Mon, 28 Apr 2003 14:41:36 -0700 (PDT) (envelope-from jonc@chen.org.nz) Received: from grimoire.chen.org.nz (localhost [127.0.0.1]) by chen.org.nz (8.12.9/8.12.9) with ESMTP id h3SLfZM4022883 for ; Tue, 29 Apr 2003 09:41:35 +1200 (NZST) (envelope-from jonc@grimoire.chen.org.nz) Received: (from jonc@localhost) by grimoire.chen.org.nz (8.12.9/8.12.9/Submit) id h3SLfZ1w022882 for freebsd-java@freebsd.org; Tue, 29 Apr 2003 09:41:35 +1200 (NZST) Date: Tue, 29 Apr 2003 09:41:35 +1200 From: Jonathan Chen To: freebsd-java@freebsd.org Message-ID: <20030428214135.GB22798@grimoire.chen.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: JDK1.4.1 and runaway processes. 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, 28 Apr 2003 21:41:38 -0000 Hi, I've been using the native JDK1.4.1 for a while now, and am happy to report that it performs very well - most of the time. However, there have been cases where the JVM appears to spawn off a new process that runs amok. The cases where this happens appears most commonly with Tomcat 4.1+, when Tomcat has to compile a jsp page. The JVM spawns off a separate process to compile a page, which then hangs and chews up processor time. On killing everything (only a -9 works), and then restarting Tomcat, a 2nd attempt to compile the page will probably succeed. Another case where this runaway process could happen is with code dealing with Printers. When a new java.awt.PrintJob is requested using java.awt.Tookit.getPrintJob, there have been times when the JVM hangs. A quick look at top(1) reveals a runaway process. What can I do to help track down this problem? It'd be nice to get a core-dump for analysis, but the processes don't seem to die unless a kill -9 is applied to it. Am I the only person to see this? System info: FreeBSD grimoire.chen.org.nz 4.8-STABLE FreeBSD 4.8-STABLE #0: Sun Apr 20 11:43:08 NZST 2003 root@grimoire.chen.org.nz:/usr/obj/usr/src/sys/GRIMOIRE i386 Running jdk-1.4.1p3_3. Cheers. -- Jonathan Chen ---------------------------------------------------------------------- "A person should be able to do a small bit of everything, specialisation is for insects"