You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2019/11/10 01:19:00 UTC

[jira] [Commented] (SUREFIRE-1713) Another "The forked VM terminated without..." type of issue

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

Tibor Digana commented on SUREFIRE-1713:
----------------------------------------

[~adolfo.cia]
I would like to ask you to try with {{3.0.0-SNAPSHOT}} version.

{code:xml}
<pluginRepository>
  <id>surefire-snapshot</id>
  <name>surefire-snapshot</name>
  <url>https://repository.apache.org/content/repositories/snapshots/</url>
  <snapshots>
    <enabled>true</enabled>
  </snapshots>
 </pluginRepository>
...
<build>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-surefire-plugin</artifactId>
      <version>3.0.0-SNAPSHOT</version>
    </plugin>
  </plugins>
</build>
{code}


You issue is similar to [#SUREFIRE-1631] and I will close it as a duplicate.
Here is my project attached in ZIP. Try to run that one. It contains your POM and a trivial test. It passed successfully.


> Another "The forked VM terminated without..." type of issue
> -----------------------------------------------------------
>
>                 Key: SUREFIRE-1713
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1713
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: JUnit 5.x support, Maven Surefire Plugin
>    Affects Versions: 2.22.2
>         Environment: Windows 10
> Maven 3.6.2
> Maven SureFire 2.22.2
> JUnit5 5.5.2
> Jmockit 1.48
> JDK 1.8.0_191
>            Reporter: Adolfo Cia
>            Priority: Major
>         Attachments: surefire-1713.zip
>
>
> Hi,
> I have a recurrent and intermittent error on the same test class of one project from the company I work for.
> It only happens in this test class, so if I annotate with @Disabled, all tests classes run successfully every time.
> Relevant configuration from my pom:
>  
> {code:java}
> <properties>
> 	<jdk.version>1.8</jdk.version>
> 	<jmockit.version>1.48</jmockit.version>
> 	<junit.version>5.5.2</junit.version>
> </properties>
> <dependencyManagement>
> 	<dependencies>
> 		<dependency>
> 			<groupId>org.junit</groupId>
> 			<artifactId>junit-bom</artifactId>
> 			<version>${junit.version}</version>
> 			<type>pom</type>
> 			<scope>import</scope>
> 		</dependency>
> 	</dependencies>
> </dependencyManagement>
> <dependencies>
> 	<dependency>
> 		<groupId>org.jmockit</groupId>
> 		<artifactId>jmockit</artifactId>
> 		<version>${jmockit.version}</version>
> 		<scope>test</scope>
> 	</dependency>
> 	<dependency>
> 		<groupId>org.junit.jupiter</groupId>
> 		<artifactId>junit-jupiter-engine</artifactId>
> 		<scope>test</scope>
> 	</dependency>
> 	<dependency>
> 		<groupId>org.junit.platform</groupId>
> 		<artifactId>junit-platform-launcher</artifactId>
> 		<scope>test</scope>
> 	</dependency>
> </dependencies>
> <build>
> 	<plugins>
> 		<plugin>
> 			<artifactId>maven-surefire-plugin</artifactId>
> 			<version>2.22.2</version>
> 			<configuration>
> 			<argLine>
> 			-javaagent:${settings.localRepository}/org/jmockit/jmockit/${jmockit.version}/jmockit-${jmockit.version}.jar
> 			</argLine>
> 			<disableXmlReport>true</disableXmlReport>
> 			</configuration>
> 		</plugin>
> 	</plugins>
> </build>
> {code}
> from target/surefire-reports the dump file 2019-11-08T16-58-51_793-jvmRun1.dump has:
>  
>  
> {code:java}
> # Created at 2019-11-08T16:58:56.656
> Killing self fork JVM. Maven process died.
> {code}
> and the output from mvn:
>  
> {code:java}
> [INFO] --- maven-surefire-plugin:2.22.2:test (default-test) @ ltl-java-linehauloperations-ensemble ---
> [INFO]
> [INFO] -------------------------------------------------------
> [INFO]  T E S T S
> [INFO] -------------------------------------------------------
> [INFO] Running com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
> ERROR StatusLogger No Log4j 2 configuration file found. Using default configuration (logging only errors to the console), or user programmatically provided configurations. Set system property 'log4j2.debug' to show Log4j 2 internal initialization logging. See https://logging.apache.org/log4j/2.x/manual/configuration.html for instructions on how to configure Log4j 2
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time:  12.833 s
> [INFO] Finished at: 2019-11-08T16:58:56-03:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project ltl-java-linehauloperations-ensemble: There are test failures.
> [ERROR]
> [ERROR] Please refer to C:\liberty_development\workspaces\services\ltl-java-linehauloperations-ensemble\target\surefire-reports for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\liberty_development\wlp\java\java\jre\bin\java -javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar -jar C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172 2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp surefire_03777119448075675073tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
> [ERROR] Command was cmd.exe /X /C "C:\liberty_development\wlp\java\java\jre\bin\java -javaagent:C:\Users\adolfo.cia\.m2\repository/org/jmockit/jmockit/1.48/jmockit-1.48.jar -jar C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172\surefirebooter6928406549506356470.jar C:\Users\adolfo.cia\AppData\Local\Temp\surefire6652798836079593172 2019-11-08T16-58-51_793-jvmRun1 surefire4400063069909447928tmp surefire_03777119448075675073tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] com.xpo.ltl.linehauloperations.service.ejb.v1.GetImageThumbnailMinuetTest
> [ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:669)
> [ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:282)
> [ERROR]         at org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1183)
> [ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1011)
> [ERROR]         at org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:857)
> [ERROR]         at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> [ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> [ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> [ERROR]         at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> [ERROR]         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> [ERROR]         at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> [ERROR]         at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
> [ERROR]         at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR]         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
> [ERROR]         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
> [ERROR]         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
> [ERROR]         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
> [ERROR]         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [ERROR]         at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
> [ERROR]         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR]         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
> [ERROR]         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> [ERROR]         at java.lang.reflect.Method.invoke(Method.java:508)
> [ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
> [ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
> [ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
> [ERROR]         at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
>  
> Things that I tried with no luck so far:
>  * change jdk
>  * change maven version
>  * change maven surefire version
>  * change jmockit version
>  * change junit5 version
>  * disable logging with src/test/resources/log4j2-test.xml
>  * maven log output to a file
>  * increase forked vm heap with argline property
> Also I check if in my code and other dependencies has a System.exit() but there isn't.
> For the last couple days this issue is driving me crazy, any help would be great!
> Thanks!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)