[ 
https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687208#comment-16687208
 ] 

Hudson commented on TIKA-2776:
------------------------------

SUCCESS: Integrated in Jenkins build tika-branch-1x #128 (See 
[https://builds.apache.org/job/tika-branch-1x/128/])
TIKA-2776 -- tika-server in legacy mode should ignore oom. (tallison: 
[https://github.com/apache/tika/commit/22f57072dfc96da6ef27e053a09f9b648552f2f2])
* (edit) tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
* (edit) tika-server/src/main/java/org/apache/tika/server/ServerStatus.java
* (edit) 
tika-server/src/test/java/org/apache/tika/server/TikaServerIntegrationTest.java
TIKA-2776 -- update CHANGES.txt (tallison: 
[https://github.com/apache/tika/commit/9e2a9bbd6e6ec6dc1ec6ecf39b6b850318df3219])
* (edit) CHANGES.txt


> Tika server child restart
> -------------------------
>
>                 Key: TIKA-2776
>                 URL: https://issues.apache.org/jira/browse/TIKA-2776
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Mario Bisonti
>            Assignee: Tim Allison
>            Priority: Blocker
>             Fix For: 2.0.0, 1.20
>
>         Attachments: log4j.xml, log4j_child.xml
>
>
> Hallo.
> I use tika server standalone started with the option:
> java -jar /opt/tika/tika-server-1.19.1.jar -spawnChild
> I use ManifoldCF and Solr to index file using tika server.
> It happens that indexing is continuously crashed because I obtain many:
> Tika down, retrying: Connection reset
> etc.
> I suspect that, when a process is restarted, the client crash as mentioned 
> here:
> _If the child process is in the process of shutting down, and it gets a new 
> request it will return 503 -- Service Unavailable. If the server times out on 
> a file, the client will receive an IOException from the closed socket. Note 
> that all other files that are being processed will end with an IOException 
> from a closed socket when the child process shuts down; e.g. if you send 
> three files to tika-server concurrently, and one of them causes a 
> catastrophic problem requiring the child to shut down, you won't be able to 
> tell which file caused the problems. In the future, we may implement a 
> gentler shutdown than we currently have._
> as reported here https://wiki.apache.org/tika/TikaJAXRS
> How could I workaround it ?
> Thanks a lot
> Mario



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to