tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TIKA-1933) ForkParser leaves tmp jars behind on Windows (at least)
Date Wed, 06 Apr 2016 13:07:25 GMT
Tim Allison created TIKA-1933:

             Summary: ForkParser leaves tmp jars behind on Windows (at least)
                 Key: TIKA-1933
                 URL: https://issues.apache.org/jira/browse/TIKA-1933
             Project: Tika
          Issue Type: Improvement
         Environment: Windows 7
            Reporter: Tim Allison
            Priority: Trivial

During the build process, the ForkParser is leaving behind its temp jars.  

I think the process is still holding onto the jar very briefly after we destroy() it.  

Java thinks the process is done -- exitValue() returns 1 and then the jar fails to be deleted.

If we add waitFor() or even a sleep(10), after we destroy(), the tmp jar is deleted.

I'm always hesitant to add an unbounded waitFor() (which we'll be able to bound in Java 8).
 Any preferences for a fix?

This message was sent by Atlassian JIRA

View raw message