Date: Tue, 2 Sep 2008 22:06:10 -0400 From: Kurt Miller <lists@intricatesoftware.com> To: freebsd-java@freebsd.org, ssanders@opnet.com Subject: Re: Possible Bug Message-ID: <200809022206.11202.lists@intricatesoftware.com> In-Reply-To: <48BDC075.2060101@opnet.com> References: <48BDC075.2060101@opnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809022206.11202.lists>