The problem was that I killed the wrong process. In my ps-ef output the worker process was unidentifiable, as the command line was lost. So I killed the wronmg one, sorry. The stack trace of the hanging test is lost L.
The child was running, but I missed to find it. Because of this it would be wonderful, if the child process could print its own PID (or the parant process print the PID of the forked process). The PID of the own Java process can be retrieved from the child by the javax.Management API! I have to lookup the code! ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Robert Muir [mailto:[email protected]] Sent: Friday, December 07, 2012 1:53 PM To: [email protected] Subject: Re: [JENKINS] Lucene-Solr-4.x-Linux (32bit/jdk1.6.0_37) - Build # 3089 - Failure! On Fri, Dec 7, 2012 at 7:48 AM, Dawid Weiss <[email protected]> wrote: Looks like the JVM waits for the forked process forever. Don't know why. but if the process is actually dead, then this loop is buggy if its still running. thats my point. i dont care what its doing, if its running by itself its in bug mode :)
