tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TIKA-1738) ForkClient does not always delete temporary bootstrap jar
Date Sun, 21 May 2017 15:40:11 GMT

     [ https://issues.apache.org/jira/browse/TIKA-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris A. Mattmann updated TIKA-1738:
------------------------------------
    Fix Version/s:     (was: 1.15)
                   1.16

> ForkClient does not always delete temporary bootstrap jar
> ---------------------------------------------------------
>
>                 Key: TIKA-1738
>                 URL: https://issues.apache.org/jira/browse/TIKA-1738
>             Project: Tika
>          Issue Type: Bug
>          Components: core
>         Environment: Windows 10
>            Reporter: Yaniv Kunda
>            Priority: Minor
>             Fix For: 1.16
>
>         Attachments: TIKA-1738.patch
>
>
> ForkClient creates a new temporary bootstrap jar each time it's instantiated, and tries
to delete it in the {{close()}} method, after destroying the process.
> Possibly a Windows-specific behavior, the OS seem to still hold a handle to the file
a bit after the process is destroyed, causing the delete() method to do nothing.
> This is recreated by simply running ForkParserTest on my machine.
> In a long-running process,this could fill the temp folder with many bootstrap jars that
will never be deleted.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message