[
https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691675#comment-16691675
]
Mario Bisonti commented on TIKA-2776:
-------------------------------------
Hallo.
I obtained, from the client calling Tika server, after 5 hours of processing
files, the error:
WARN 2018-11-19T13:47:17,888 (Worker thread '56') - Service interruption
reported for job 1533797717712 connection 'WinShare': Tika down, retrying:
Connect to hostanmeubuntu:9998 [hostanmeubuntu/172.16.1.135] failed: Connection
refused (Connection refused)
WARN 2018-11-19T13:47:18,006 (Worker thread '96') - Service interruption
reported for job 1533797717712 connection 'WinShare': Tika down, retrying:
Connect to hostanmeubuntu:9998 [hostanmeubuntu/172.16.1.135] failed: Connection
refused (Connection refused)
WARN 2018-11-19T13:47:18,006 (Worker thread '20') - Service interruption
reported for job 1533797717712 connection 'WinShare': Tika down, retrying:
Connect to hostanmeubuntu:9998 [hostanmeubuntu/172.16.1.135] failed: Connection
refused (Connection refused)
WARN 2018-11-19T13:47:18,071 (Worker thread '26') - Service interruption
reported for job 1533797717712 connection 'WinShare': Tika down, retrying:
Connect to hostanmeubuntu:9998 [hostanmeubuntu/172.16.1.135] failed: Connection
refused (Connection refused)
WARN 2018-11-19T13:47:18,116 (Worker thread '27') - JCIFS: Possibly transient
exception detected on attempt 1 while getting share security: All pipe
instances are busy.
Perhaps it could be to:
_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._
Perhaps could a gentler shutdown solve the problem?
Thanks
Mario
> 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)
