tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1933) ForkParser leaves tmp jars behind on Windows (at least)
Date Tue, 08 Nov 2016 03:56:58 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646397#comment-15646397
] 

Hudson commented on TIKA-1933:
------------------------------

SUCCESS: Integrated in Jenkins build tika-2.x #171 (See [https://builds.apache.org/job/tika-2.x/171/])
TIKA-1933 - clean up one more place where we aren't closing the (tallison: rev 1d1bc0dd7a145651f62bd93b363b0247035f1c00)
* (edit) tika-app/src/test/java/org/apache/tika/parser/fork/ForkParserIntegrationTest.java


> 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: Sub-task
>         Environment: Windows 7
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 1.13
>
>
> 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
(v6.3.4#6332)

Mime
View raw message