You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/02/16 17:22:00 UTC

[jira] [Resolved] (TIKA-3301) Simplify forking/monitoring in tika-server for 2.x

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

Tim Allison resolved TIKA-3301.
-------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> Simplify forking/monitoring in tika-server for 2.x
> --------------------------------------------------
>
>                 Key: TIKA-3301
>                 URL: https://issues.apache.org/jira/browse/TIKA-3301
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> In looking back at the code for tika-server's forking process and monitoring. We can simplify it quite a bit and make restarts more timely and efficient.
> We should change a few Thread.sleep calls to process.waitFor() so that we're notified instantly if a forked process dies.
> We don't need the pinging communication via stdout/stdin between forking and forked.  The forking process can monitor the forked process via the forkedstatusfile and watching for an exit value.  The forked process can monitor its parent by blocking on a read of stdin. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)