[
https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697249#comment-16697249
]
Mario Bisonti commented on TIKA-2776:
-------------------------------------
Yes, there were any files processed in the interval 13:24-13:34
No files processed after because the job crashed as you can see from the
MCF_JOB.png
I tried to start tika server with the two log specification but it doesn't work.
I obtain the error:
administrator@sengvivv02:/opt/tika$ sudo -u tomcat java -jar
/opt/tika/tika-server-1.19.1.jar -Dlog4j.configuration=file:/opt/tika/log4j.xml
-JDlog4j.configuration=file:/opt/tika/log4j_child.xml --host=sengvivv02
-spawnChild
Nov 23, 2018 3:55:45 PM org.apache.tika.config.InitializableProblemHandler$3
handleInitializableProblem
WARNING: J2KImageReader not loaded. JPEG2000 files will not be processed.
See https://pdfbox.apache.org/2.0/dependencies.html#jai-image-io
for optional dependencies.
Nov 23, 2018 3:55:45 PM org.apache.tika.config.InitializableProblemHandler$3
handleInitializableProblem
WARNING: org.xerial's sqlite-jdbc is not loaded.
Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
INFO Starting Apache Tika 1.19.1 server
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option:
-Dlog4j.configuration=file:/opt/tika/log4j.xml
at org.apache.commons.cli.Parser.processOption(Parser.java:363)
at org.apache.commons.cli.Parser.parse(Parser.java:199)
at org.apache.commons.cli.Parser.parse(Parser.java:85)
at org.apache.tika.server.TikaServerCli.execute(TikaServerCli.java:133)
at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:117)
ERROR Can't start:
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option:
-Dlog4j.configuration=file:/opt/tika/log4j.xml
at org.apache.commons.cli.Parser.processOption(Parser.java:363)
at org.apache.commons.cli.Parser.parse(Parser.java:199)
at org.apache.commons.cli.Parser.parse(Parser.java:85)
at org.apache.tika.server.TikaServerCli.execute(TikaServerCli.java:133)
at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:117)
> 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: Log.zip, MCF_JOB.png, log4j.xml, log4j_child.xml,
> log4j_child.xml, tikalogchild.log
>
>
> 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)
