Uploaded image for project: 'Tika'
  1. Tika
  2. TIKA-1936 Clean up parsers not cleaning up resources
  3. TIKA-1933

ForkParser leaves tmp jars behind on Windows (at least)

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • None
    • 1.13
    • None
    • None
    • Windows 7

    Description

      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?

      Attachments

        Activity

          People

            Unassigned Unassigned
            tallison Tim Allison
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: