threads/78660: Java hangs unkillably in STOP state after fork()
Thomas Lange
thomas.lange at techunity.de
Thu Mar 10 06:30:04 GMT 2005
>Number: 78660
>Category: threads
>Synopsis: Java hangs unkillably in STOP state after fork()
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-threads
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Mar 10 06:30:03 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Thomas Lange
>Release: 5.3 Release
>Organization:
>Environment:
FreeBSD hellraiser.smega.com 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #2: Fri Feb 18 17:19:29 CET 2005 root at hellraiser.smega.com:/usr/obj/usr/src/sys/HELLRAISER-05-02-02 i386
>Description:
After many calls of Runtime.getRuntime().exec(), which starts an external process, Java hangs reproducably in a STOP state and cannot be killed. (Not even with kill -9)
>How-To-Repeat:
Run any Java application, which makes extensive use of Runtime.getRuntime().exec().
With my application, I can reproduce the problem within an hour or so - on two different machines.
>Fix:
Apply David Xu's patch to kern_thread.c as described in
http://lists.freebsd.org/pipermail/freebsd-current/2004-November/042407.html
That change is also commited to 5.3-stable.
However, maybe someone with a thorough understanding of the internal kernel structure should have a look at it.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-threads
mailing list