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 2026/05/27 14:09:00 UTC

[jira] [Resolved] (TIKA-4740) Flaky timeout on Windows

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

Tim Allison resolved TIKA-4740.
-------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

I think this is fixed. The issue was that when tika-server's process was killed, pipesserver wasn't shutting down quickly on windows. We added a hook that should make that faster.

We tried to leave the default inheritIO active because that's the norm in docker/k8s etc. We do not want to log to file by default nowadays.

> Flaky timeout on Windows
> ------------------------
>
>                 Key: TIKA-4740
>                 URL: https://issues.apache.org/jira/browse/TIKA-4740
>             Project: Tika
>          Issue Type: Task
>          Components: tika-pipes
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 4.0.0
>
>
> We're getting a flaky timeout in windows in the unpack tests.
> e.g.: [https://github.com/apache/tika/actions/runs/26470635995/job/77942835729]
>  
> This may be caused because we're inheriting IO. We don't need to do this anymore because comms are through a port. Let's stop inheriting IO between client and server where possible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)