From owner-freebsd-java@FreeBSD.ORG Mon Apr 28 15:23:44 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 EA5E437B40E for ; Mon, 28 Apr 2003 15:23:44 -0700 (PDT) Received: from azrael.xs4all.nl (azrael.xs4all.nl [213.84.50.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D8543FAF for ; Mon, 28 Apr 2003 15:23:43 -0700 (PDT) (envelope-from remco@azrael.xs4all.nl) Received: from azrael.xs4all.nl (localhost [127.0.0.1]) by azrael.xs4all.nl (8.12.8p1/8.12.8) with ESMTP id h3SMNgaE005307 for ; Tue, 29 Apr 2003 00:23:42 +0200 (CEST) (envelope-from remco@azrael.xs4all.nl) Received: (from remco@localhost) by azrael.xs4all.nl (8.12.8p1/8.12.8/Submit) id h3SMNgZC005306 for freebsd-java@freebsd.org; Tue, 29 Apr 2003 00:23:42 +0200 (CEST) Date: Tue, 29 Apr 2003 00:23:42 +0200 From: "Remco van 't Veer" To: freebsd-java@freebsd.org Message-ID: <20030428222342.GC82809@azrael.xs4all.nl> References: <20030428214135.GB22798@grimoire.chen.org.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030428214135.GB22798@grimoire.chen.org.nz> X-Spook: recondo rhost EIP CCC Flintlock Military Intelligence XS4ALL WANK User-Agent: Mutt/1.5.4i Subject: Re: 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 22:23:45 -0000 I am experiencing the same problem with tomcat-4.1 here, on a 4.8-RELEASE with jdk-1.4.1p3_3. The problem doesn't always occur and the runaway process keeps running when I stop tomcat. Remco On Tue, Apr 29, 2003 at 09:41, Jonathan Chen wrote: > 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.