Affects Version/s: 2.8
Fix Version/s: None
Component/s: process forking
Environment:64 bit RHEL 5.5 , 64-bit Java 1.6.0_23
Our forked JUnit/surefire processes are not always stopping correctly when timing out within a Maven build
(running inside our Jenkins CI server, ver 1.425).
The maven build finishes and Jenkins shows a failed/unstable build.
These running processes cause problems later, because the tests may be holding a resource like a port, and subsequent rebuilds fail because the
For example, even though no Maven builds are currently running, ps shows about a dozen Java processes running,
with commands such as:
We have our Maven surefire preferences set to fork the tests (via a parent pom)
I suspect the timeout is the problem - i.e. perhaps the test is timing out and the attempt to kill the forked process
fails, leaving it running.
Has anyone seen something similar and/or know how to fix this so that surefire really kills the process?
When this happens, doing
(logged in as the process owner) usually does not work, but
kill -9 <processid>