[
https://issues.apache.org/jira/browse/TIKA-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286160#comment-17286160
]
Hudson commented on TIKA-3301:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #165 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/165/])
TIKA-3301 -- small cleanups in tika-server (tallison:
[https://github.com/apache/tika/commit/af7b2e62bcc99e48023fa60da0945ec6e3469170])
* (delete) tika-server/tika-server-core/src/main/resources/log4j.properties
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/TikaServerConfig.java
* (add) tika-server/tika-server-classic/src/main/resources/log4j.properties
* (edit)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/CXFTestBase.java
> Simplify forking/monitoring in tika-server for 2.x
> --------------------------------------------------
>
> Key: TIKA-3301
> URL: https://issues.apache.org/jira/browse/TIKA-3301
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 2.0.0
>
>
> In looking back at the code for tika-server's forking process and monitoring.
> We can simplify it quite a bit and make restarts more timely and efficient.
> We should change a few Thread.sleep calls to process.waitFor() so that we're
> notified instantly if a forked process dies.
> We don't need the pinging communication via stdout/stdin between forking and
> forked. The forking process can monitor the forked process via the
> forkedstatusfile and watching for an exit value on the process. The forked
> process can monitor its parent by blocking on a read of stdin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
