[ https://issues.apache.org/jira/browse/TIKA-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16694671#comment-16694671 ]
Tim Allison commented on TIKA-2776: ----------------------------------- If you're using 1.19.1, you've hit TIKA-2785. The temporary fix is to have the ConsoleAppender write to stderr: {noformat} <appender name="console" class="org.apache.log4j.ConsoleAppender"> <param name="target" value="System.err"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d\{yyyy-MM-dd HH:mm:ss} %-5p %c\{1}:%L - %m%n" /> </layout> </appender> {noformat} I tested this with 1.19.1 on Windows, and I had success. If you have an interest in testing the new mechanism, grab a nightly build of tika-server from, e.g. [here|https://builds.apache.org/job/tika-branch-1x/131/org.apache.tika$tika-server/artifact/org.apache.tika/tika-server/1.20-20181120.215531-52/tika-server-1.20-20181120.215531-52.jar], and you can use the log file as you had it configured. :D > 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)