[
https://jira.codehaus.org/browse/SUREFIRE-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356030#comment-356030
]
Tibor Digana commented on SUREFIRE-859:
---------------------------------------
@Mag would you have time to check the fix with new snapshot version?
The same JVM and machine should be used again.
> Exception in thread "TreadedStreamConsumer" java.lang.RuntimeException during
> GC
> --------------------------------------------------------------------------------
>
> Key: SUREFIRE-859
> URL: https://jira.codehaus.org/browse/SUREFIRE-859
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Surefire Plugin,
> process forking
> Affects Versions: 2.11, 2.12
> Environment: Solaris 5.10, jdk16-1.6.0_11-0 (same with jdk1.5.0_14),
> apache-maven-2.2.1
> Reporter: Mag Hoehme
> Assignee: Tibor Digana
> Attachments: runtimeexception.txt
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
