[
https://issues.apache.org/jira/browse/TIKA-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3469:
------------------------------
Description: Our jdk11 builds are failing on Jenkins because the pipes
processor client is receiving unexpected bytes from the forked process. The
jvm is likely writing warnings to stdout from the forked process before the
forked process redirects stdout. We should consume and log bytes before the
'ready' byte from the forked process as we currently do in the ForkParser.
(was: Our jdk11 builds are failing on Jenkins because the pipes processor
client is receiving unexpected bytes from the forked process. The jvm is
likely writing warnings to stdout from the forked process before the forked
process redirects stdout. We should add a 'ready' ping from the forked process
and have the client ignore everything until the 'ready' byte is read as we
currently do in the ForkParser.)
> Consume bytes until 'ready' ping to forked pipes processor
> ----------------------------------------------------------
>
> Key: TIKA-3469
> URL: https://issues.apache.org/jira/browse/TIKA-3469
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
>
> Our jdk11 builds are failing on Jenkins because the pipes processor client is
> receiving unexpected bytes from the forked process. The jvm is likely
> writing warnings to stdout from the forked process before the forked process
> redirects stdout. We should consume and log bytes before the 'ready' byte
> from the forked process as we currently do in the ForkParser.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
