[
https://issues.apache.org/jira/browse/TIKA-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693763#comment-16693763
]
Hudson commented on TIKA-2785:
------------------------------
UNSTABLE: Integrated in Jenkins build tika-2.x-windows #352 (See
[https://builds.apache.org/job/tika-2.x-windows/352/])
TIKA-2785 -- clean up logging in tika-server; redirect child stdout to
(tallison: rev 4aae9251b26180377bfa44c3720aa4bfac29b81b)
* (add)
tika-server/src/test/java/org/apache/tika/server/NullWebClientLogger.java
* (edit)
tika-server/src/test/java/org/apache/tika/server/TikaServerIntegrationTest.java
* (add) tika-server/src/test/resources/log4j.properties
* (edit)
tika-server/src/main/java/org/apache/tika/server/TikaServerWatchDog.java
* (add) tika-server/src/test/resources/mock/fake_oom.xml
> Switch parent/child IPC to mmap file from stdout/stderr in tika-server
> ----------------------------------------------------------------------
>
> Key: TIKA-2785
> URL: https://issues.apache.org/jira/browse/TIKA-2785
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0, 1.20
>
>
> When I added {{-spawnChild}} to tika-server, I followed the pattern in
> ForkParser of redirecting stdout/stderr for the parent to listen to output
> from the child process. This relies on the parsers not grabbing a pointer to
> stdout/stderr _before_ we redirect it. However, it is possible for parsers
> to grab stdout/stderr during static initialization, as happens with log4j
> configured to write to stdout/stderr.
> This means that the communication channel from child to parent is unreliable.
> Let's switch child to parent communication in {{-spawnChild}} to a shared
> mmap'd file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
