[SUREFIRE-1722] JVM is not killed after forkedProcessTimeoutInSeconds has elapsed

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.0-M4
• Component/s: Maven Surefire Plugin

Environment

Debian 4.9.168-1+deb9u5 (2019-08-11) x86_64
Apache Maven 3.3.9
Maven home: /usr/share/maven
Java version: 1.8.0_232, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.9.0-9-amd64", arch: "amd64", family: "unix"

• Assignee: Unassigned
• Reporter: John Bergqvist
• Created: 18/Nov/19 13:43
• Updated: 29/Aug/24 13:03

Description

I frequently encounter situations where after setting the forkedProcessTimeoutInSeconds property, a JVM with a test that hangs is not killed after the settings have elapsed.

I have attached the particular test (tika-example/src/test/java/org/apache/tika/example/DirListParserTest.java), which is is used as an example to demonstrate a test that causes the JVM to hang, and have configured my surefire plugin as follows (junit 4.12):

 

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>3.0.0-M4</version>
        <configuration>
          <enableProcessChecker>all</enableProcessChecker>
          <forkCount>0.5C</forkCount>
          <forkedProcessTimeoutInSeconds>5</forkedProcessTimeoutInSeconds>
          <forkedProcessExitTimeoutInSeconds>5</forkedProcessExitTimeoutInSeconds>
          <reuseForks>false</reuseForks>
        </configuration>
      </plugin>