[
https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694777#comment-16694777
]
Tim Allison commented on TIKA-2776:
-----------------------------------
Sorry. I do have a file produced on the file system. I just attached the
literal .xml log config file and the log that was written to my file system.
{noformat}
C:\data\tika_server>java -jar tika-server-1.19.1.jar
-JDlog4j.configuration=file:log4j_child.xml -spawnChild
Nov 21, 2018 9:30:08 AM 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 21, 2018 9:30:08 AM 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
Nov 21, 2018 9:30:09 AM 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 21, 2018 9:30:09 AM 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.
2018-11-21 09:30:09 INFO TikaServerCli:115 - Starting Apache Tika 1.19.1 server
2018-11-21 09:30:09 INFO ServerImpl:85 - Setting the server's publish address
to be http://localhost:9998/
2018-11-21 09:30:09 INFO log:193 - Logging initialized @1296ms to
org.eclipse.jetty.util.log.Slf4jLog
2018-11-21 09:30:09 INFO Server:374 - jetty-9.4.z-SNAPSHOT; built:
2018-06-05T18:24:03.829Z; git: d5fc0523cfa96bfebfbda19606cad384d772f04c; jvm
1.8.0_192-b12
2018-11-21 09:30:10 INFO AbstractConnector:289 - Started
ServerConnector@1af2d44a{HTTP/1.1,[http/1.1]}{localhost:9998}
2018-11-21 09:30:10 INFO Server:411 - Started @1811ms
2018-11-21 09:30:10 WARN ContextHandler:1572 - Empty contextPath
2018-11-21 09:30:10 INFO ContextHandler:851 - Started
o.e.j.s.h.ContextHandler@342c38f8{/,null,AVAILABLE}
2018-11-21 09:30:10 INFO TikaServerCli:316 - Started Apache Tika server at
http://localhost:9998/
2018-11-21 09:30:27 INFO RecursiveMetadataResource:429 - rmeta (autodetecting
type){noformat}
I then curled a file a couple of times against the server:
{noformat}
curl.exe -T somePDF.pdf http://localhost:9998/rmeta
{noformat}
> 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, 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)
