[
https://issues.apache.org/jira/browse/TIKA-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043937#comment-18043937
]
Hudson commented on TIKA-4556:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1089 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1089/])
TIKA-4556 - fix pipes client/server protocol bug (github:
[https://github.com/apache/tika/commit/3eba834f507cf3d6e721a421bf51c3110744bdce])
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/PipesClient.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/PipesServer.java
* (edit)
tika-pipes/tika-pipes-integration-tests/src/test/java/org/apache/tika/pipes/core/PipesClientTest.java
> Swap stdout/stdin channel in pipes-server for localhost socket
> --------------------------------------------------------------
>
> Key: TIKA-4556
> URL: https://issues.apache.org/jira/browse/TIKA-4556
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Fix For: 4.0.0
>
>
> The pipes client and pipes server currently communicate via stdout/stdin
> following the model of the ForkParser. This can get messy if loggers start
> writing to stdout before pipes server can redirect the stream.
> The other benefit of a socket is that we can set timeouts that are monitored
> by the operating system...rather than having to set up our own watchers.
> We should simplify the channel to a localhost socket and do a simple inherit
> io in the pipes client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
