[
https://issues.apache.org/jira/browse/SUREFIRE-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258419#comment-16258419
]
Tibor Digana edited comment on SUREFIRE-1444 at 11/19/17 10:18 AM:
-------------------------------------------------------------------
[~rfsnjb]
It's very difficult to say what's going to from this stack trace. The trace
should be deleted in the future.
This is important:
{{Killing self fork JVM. Maven process died.}}
Why your Maven process has died on Windows?
Did your Garbage Collector in JVM block Maven?
Can you dump CPU from JMX and GC in Maven process and in Surefire process?
Post your project link.
was (Author: tibor17):
[~rfsnjb]
It's very difficult to say what's going to from this stack trace. The trace
should be deleted in the future.
This is important:
{{Killing self fork JVM. Maven process died.}}
Why your Maven process has died on Windows?
Did your Garbage Collector in JVM blocked Maven?
Can you dump CPU from JMX and GC in Maven process and in Surefire process?
Post your project link.
> org.apache.maven.surefire.booter.SurefireBooterForkException
> ------------------------------------------------------------
>
> Key: SUREFIRE-1444
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1444
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.20.1
> Environment: Windows 7 Pro 64 bits
> Maven 3.5.2 , jdk 1.8.0_152
> Reporter: rfs
> Assignee: Tibor Digana
>
> mvn test is failed with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.20.1
> maven repository is deleted before but same result.
> mvn test is successfull with maven 3.5.2, jdk 1.8.0_x, maven surefire 2.19.1
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 9.490 s
> [INFO] Finished at: 2017-11-16T08:58:19+01:00
> [INFO] Final Memory: 35M/290M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on
> project project-name: There are test fa
> ilures.
> [ERROR]
> [ERROR] Please refer to R:\src\project-name\target\surefire-reports for the
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] The forked VM terminated without properly saying goodbye. VM crash or
> System.exit called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The
> forked VM terminated without properly saying goodbye. VM crash or System.exi
> t called?
> [ERROR] Command was cmd.exe /X /C "R:\tools\jdk1.8.0_152\jre\bin\java -jar
> d:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195\sur
> efirebooter7359328160006854832.jar
> D:\Profiles\XXX\AppData\Local\Temp\surefire4973827123764606195
> 2017-11-16T08-58-14_352-jvmRun1 surefire80634
> 62497440390334tmp surefire_0627218662296028436tmp"
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:686)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:535)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:280)
> [ERROR] at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:245)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> [ERROR] at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> [ERROR] at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> [ERROR] at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> [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:51)
> [ERROR] at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> [ERROR] at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> [ERROR] at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> [ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:955)
> [ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:290)
> [ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:194)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:498)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> [ERROR] at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> [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
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :project-name
> 'cmd' n'est pas reconnu en tant que commande interne
> ou externe, un programme exécutable ou un fichier de commandes.
> dump file : ******-jvmRun1.dump
> Killing self fork JVM. Maven process died.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
