maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sander Wozniak (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SUREFIRE-1541) SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
Date Wed, 07 Nov 2018 10:03:00 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677944#comment-16677944
] 

Sander Wozniak edited comment on SUREFIRE-1541 at 11/7/18 10:02 AM:
--------------------------------------------------------------------

We have observed the same issue in our Java 8 project (both inside and outside of Docker).
It seems to also affect older releases of the plugin (2.19.1). Maven 3.6.0 and 3.5.4 did not
work, downgrading to 3.5.3 seems to solve the issue.


was (Author: sawo):
We have observed the same issue in our project (both inside and outside of Docker). It seems
to also affect older releases of the plugin (2.19.1). Maven 3.6.0 and 3.5.4 did not work,
downgrading to 3.5.3 seems to solve the issue.

> SurefireBooterForkException: The forked VM terminated without properly saying goodbye.
VM crash or System.exit called?
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1541
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1541
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.22.0
>            Reporter: Anghel Botos
>            Priority: Major
>
> Attempting to run integration tests using maven-failsafe-plugin with {{-Dmaven.failsafe.debug=false}}
yields the following stacktrace:
>  
> {noformat}
> [ERROR] ExecutionException The forked VM terminated without properly saying goodbye.
VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C ""C:\Program Files\Java\jdk1.8.0_121\jre\bin\java" false
-jar C:\Users\ANGHEL~1.BOT\AppData\Local\Temp\surefire8539836821793811485\surefirebooter6734575521909210279.jar
C:\Users\anghel.botos\AppData\Local\Temp\surefire8539836821793811485 2018-07-24T11-18-12_704-jvmRun1
surefire7184511894589995478tmp surefire_411836142070426630764tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:494)
> [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:441)
> [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:293)
> [ERROR] at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> {noformat}
>  
> The issue is the "free-floating" {{false}} that appears in the command line used to
start a new JVM. I've traced down the issue to {{org.apache.maven.plugin.surefire.AbstractSurefireMojo#getEffectiveDebugForkedProcess}}
where the following code can be found:
> {code:java}
>         String debugForkedProcess = getDebugForkedProcess();
>         if ( "true".equals( debugForkedProcess ) )
>         {
>             return "-Xdebug -Xnoagent -Djava.compiler=NONE"
>                 + " -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005";
>         }
>         return debugForkedProcess;
> {code}
> ...which is quite..."unexpected" to see that one can pass in a value of {{true}}, but
not a value of {{false}}.
> Please fix with a proper parsing of true/false values for the {{maven.failsafe.debug}}
property.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message