[jira] [Resolved] (TIKA-3588) Fix thread starvation in PipesClient after numerous restarts

["Tim Allison (Jira)" <ji...@apache.org>]

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

Tim Allison resolved TIKA-3588.
-------------------------------
    Fix Version/s: 2.1.1
         Assignee: Tim Allison
       Resolution: Fixed

We need to make sure to close the input/output streams from the PipesClient process to ensure that the parsing-monitoring thread in that process correctly ends.  I also added more logging.

> Fix thread starvation in PipesClient after numerous restarts
> ------------------------------------------------------------
>
>                 Key: TIKA-3588
>                 URL: https://issues.apache.org/jira/browse/TIKA-3588
>             Project: Tika
>          Issue Type: Bug
>          Components: tika-pipes
>    Affects Versions: 2.1.0
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>             Fix For: 2.1.1
>
>
> I've noticed that PipesClient was not correctly restarting the PipesServer. With enough logging, it is clear that the thread to check whether the server has started is itself never called/run.  Via debug logging, I can see that the PipesServer is starting correctly and sending the ready byte fairly quickly.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)