[
https://issues.apache.org/jira/browse/TIKA-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230973#comment-15230973
]
Hudson commented on TIKA-1933:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #948 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/948/])
TIKA-1933 (tallison: rev 61d8ec7534e91bdc994456e1883a5d07abf2037c)
* tika-core/src/main/java/org/apache/tika/fork/ForkClient.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
>
> 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)
