1. 技术文章
  2. Maven build and maven-failsafe-plugin - The forked VM terminated without properly saying goodbye

Maven build and maven-failsafe-plugin - The forked VM terminated without properly saying goodbye

由 大兔子大兔子 提交于 2019-11-29 13:31:46

I have the same problem and found three solutions which working for me:

Problem description

Problem is with maven plugin maven-surefire-plugin only in version 2.20.1 and 2.21.0. I checked and you use version 2.20.1.

Solution 1

Upgrade plugin version to 2.22.0. Add in pom.xml:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.22.0</version>
</plugin>

Solution 2

Downgrade plugin version to 2.20. Add in pom.xml:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.20</version>
</plugin>

Solution 3

Use plugin configuration testFailureIgnore. Add in pom.xml:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <configuration>
    <testFailureIgnore>true</testFailureIgnore>
  </configuration>
</plugin>

VM can crash because of many reasons. I am highlighting here one more cause it can crash.

I was using maven-surefire-plugin version 2.22.0 with jvm config -Xmx2048m but still it was failing for me.

Cause of failure: Accidentally I changed windows command prompt 'window buffer size' width to 2000 instead of changing the height. It causes the vm crashes in my case. When i ran the build using git bash it worked fine. So I able to figure out the issue and reverted the command prompt 'window buffer size' width to default value and it worked fine for me.

Troubleshooting step:

  • Use different command tool to verify this issue. like window command prompt, git bash.

I'm also have error like that, related with forkstarter on the surefire plugin maybe you can try add this on your pom.xml

        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
                <argLine>--add-modules java.base ${argLine} -Xmx1024m -XX:MaxPermSize=256m</argLine>
                <forkCount>3</forkCount>
                <reuseForks>true</reuseForks>
            </configuration>
        </plugin>

Hope, this can help you

I use the maven-surefire-plugin:2.22.1, but the forked VM still crashes. In my case the configuration forkedProcessExitTimeoutInSeconds for the maven-surefire-plugin helps. The default value are since maven-surefire-plugin:2.20.1 30 seconds. My project gots very time consuming test and so the forked JVM chrashes. Configure the plugin in the pom with the following property solves the problem.

<plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
                <forkedProcessExitTimeoutInSeconds>120</forkedProcessExitTimeoutInSeconds>
        </configuration>
</plugin>
Sounak Saha

Try out with Manven OPT parameter

export MAVEN_OPTS="-Xms1024m -Xmx1G -XX:PermSize=1024m -noverify"

标签
java
maven
Docker
windows-10
maven-surefire-plugin
易学教程内所有资源均来自网络或用户发布的内容，如有违反法律规定的内容欢迎反馈！
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!