Dan Berindei created SUREFIRE-1524:
--------------------------------------

             Summary: PpidChecker sometimes writes dump file with IOException
                 Key: SUREFIRE-1524
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1524
             Project: Maven Surefire
          Issue Type: Bug
          Components: process forking
    Affects Versions: 2.21.0
            Reporter: Dan Berindei


We have a build with lots of modules, and once in a while we see a dump file 
like this after the build:
{noformat}
./commons/target/surefire-reports/2018-05-26T05-53-09_562-jvmRun1.dump
# Created on 2018-05-26T05:53:16.823
java.io.IOException: Stream closed
        at 
java.base/java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:176)
        at 
java.base/java.io.BufferedInputStream.read1(BufferedInputStream.java:289)
        at 
java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:351)
        at java.base/sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at java.base/sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at java.base/sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.base/java.io.InputStreamReader.read(InputStreamReader.java:185)
        at java.base/java.io.Reader.read(Reader.java:104)
        at java.base/java.util.Scanner.readInput(Scanner.java:882)
        at java.base/java.util.Scanner.findWithinHorizon(Scanner.java:1796)
        at java.base/java.util.Scanner.hasNextLine(Scanner.java:1610)
        at 
org.apache.maven.surefire.booter.PpidChecker$ProcessInfoConsumer.execute(PpidChecker.java:301)
        at 
org.apache.maven.surefire.booter.PpidChecker.unix(PpidChecker.java:160)
        at 
org.apache.maven.surefire.booter.PpidChecker.isProcessAlive(PpidChecker.java:115)
        at 
org.apache.maven.surefire.booter.ForkedBooter$2.run(ForkedBooter.java:213)
<...>


# Created on 2018-05-26T05:53:16.827
System.exit() or native command error interrupted process checker.{noformat}
Looks like it's safe to ignore both messages, but it would be better if they 
weren't logged at all.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to