[
https://issues.apache.org/jira/browse/TIKA-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440701#comment-17440701
]
Hudson commented on TIKA-3588:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #353 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/353/])
TIKA-3588 -- Fix thread starvation after numerous restarts in PipesClient
(tallison:
[https://github.com/apache/tika/commit/36362c6b3e7238b2d29e143d876d412f0f1f0fa2])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit) CHANGES.txt
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
> 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)
