Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.11, 2.12
-
Fix Version/s: None
-
Component/s: Junit 4.7+ (parallel) support, Maven Surefire Plugin, process forking
-
Labels:None
-
Environment:Solaris 5.10, jdk16-1.6.0_11-0 (same with jdk1.5.0_14), apache-maven-2.2.1
-
Complexity:Intermediate
-
Number of attachments :
Description
When executing 151 integration tests with 829 test methods on a Solaris machine, there is an exception:
===
Exception in thread "ThreadStreamConsumer" java.lang.RuntimeException: 176: [GC 100,177: [ParNew
...
java.langh.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
===
(see attachment for full stack traces)
The message of the RuntimeException suggests that the problem is connected to garbage collection. The stack trace points to ForkClient.java. It looks as if the method "consumeLine" in ForkClient.java is fed with GC information instead of the expected string.
The exception occurs with concurrency configuration "parallel='none'" as well as with "parallel='classes'" in both versions of the surefire plugin, 2.11 and 2.12.
However, this problem does not show up on a Windows/Cygwin environment.
