From owner-freebsd-java@FreeBSD.ORG Wed Sep 3 13:58:56 2008 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DCCA1065681 for ; Wed, 3 Sep 2008 13:58:56 +0000 (UTC) (envelope-from ssanders@opnet.com) Received: from enterprise58.opnet.com (enterprise58.opnet.com [192.104.65.21]) by mx1.freebsd.org (Postfix) with ESMTP id DBA968FC13 for ; Wed, 3 Sep 2008 13:58:55 +0000 (UTC) (envelope-from ssanders@opnet.com) Received: from [172.16.12.251] (wtn12251.opnet.com [172.16.12.251]) by enterprise58.opnet.com (8.13.6/8.12.10) with ESMTP id m83CwGXG006702; Wed, 3 Sep 2008 08:58:16 -0400 Message-ID: <48BE981A.4090109@opnet.com> Date: Wed, 03 Sep 2008 09:58:50 -0400 From: Stephen Sanders Organization: OpNet User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: kurt@intricatesoftware.com References: <48BDC075.2060101@opnet.com> <200809022206.11202.lists@intricatesoftware.com> In-Reply-To: <200809022206.11202.lists@intricatesoftware.com> X-Enigmail-Version: 0.95.7 Content-Type: multipart/mixed; boundary="------------030006000402060903030706" X-OPNET-MailScanner: Found to be clean X-MailScanner-From: ssanders@opnet.com X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-java@freebsd.org Subject: Re: Possible Bug X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ssanders@opnet.com List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2008 13:58:56 -0000 This is a multi-part message in MIME format. --------------030006000402060903030706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I'm sorry, oversight on my part. It is 6.3 that's having the problem. Thanks for the pointer. Kurt Miller wrote: > On Tuesday 02 September 2008 6:38:45 pm Stephen Sanders wrote: > >> We have an application that fork/execs processes at a low frequency rate >> ( ~1/minute). The system is under a reasonably heavy >> processor/network/disk load as it is capturing data at 1Gbps+. >> >> At what appear to be random intervals, the parent process in the fork >> starts consuming 100% CPU. It looks like the monitor thread in >> UNIXProcess is the culprit. >> >> I've not been able to down load the diablo patches from the FreeBSD web >> site, however, it appears OpenJDK that there may be a window for this >> sort of thing to happen in UNIXProcess_md.c. >> >> In Java_java_lang_UNIXProcess_waitForExit(), waitpid() could very easily >> fail returning an EINTR as there are no options to the waitpid call.. >> This will could cause a tight loop. The error section of the man page >> says that if WNOHANG is NOT set then unblocked signals or SIGCHLD will >> cause EINTR errors. >> >> I'll attempt to get the patches from the eyesbeyond web site and verify >> this claim. >> >> Thanks for your attention. >> >> >> > > You didn't mention which FreeBSD version you are running. If it is 6.3 > you need to apply this errata to fix a pthread fork bug that exhibits > the symptoms you have described: > > http://security.freebsd.org/advisories/FreeBSD-EN-08:01.libpthread.asc > > The need for this errata on 6.3 is described in the RELEASENOTE.txt file > that comes with diablo. > > -Kurt > > > --------------030006000402060903030706--