Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-1722

JVM is not killed after forkedProcessTimeoutInSeconds has elapsed

    XMLWordPrintableJSON

    Details

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

      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>
      

        Attachments

        1. DirListParserTest.java
          0.3 kB
          John Bergqvist

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              JohnLBergqvist John Bergqvist
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: