[
https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686689#comment-16686689
]
Mario Bisonti commented on TIKA-2776:
-------------------------------------
Hallo Tim.
# The error "Caused by: java.lang.OutOfMemoryError: Java heap space" happened
when I tried to use Tika, launching
java -jar /opt/tika/tika-server-1.19.1.jar
so WITHOUT the option "-spawnChild.
# When you said _The other thing you might want to do...if you aren't
already...is add a {{waitForServer}} loop along the lines of what I did in
TikaServerIntegrationTest...for when your client hits a 503._
Do you mean to put the code that you mention, in the client that calls tika
server?
In my case ManifoldCF ?
If yes, I will forward your suggestion to the ManifoldCF owner
# Now I tried to start tika server in my windows host, to split ManildCF-Solr
and Tika server, and the job is working by 5 hours without crash!
Note that in my widows host I use:
java -version
java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)
instead, in the Ubuntu host, where there are ManildCF-Solr and where I used,
before this test of splitting, the tika server with the job that stpped
repeatedly, I use:
java -version
openjdk version "10.0.2" 2018-07-17
OpenJDK Runtime Environment (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.3)
OpenJDK 64-Bit Server VM (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.3, mixed mode)
Do you know if there is any issue about the java version where tika server runs?
Thanks a lot a lot.
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
> Priority: Major
> 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)
