[ 
https://issues.apache.org/jira/browse/TIKA-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16855892#comment-16855892
 ] 

Thomas van Hesteren commented on TIKA-2889:
-------------------------------------------

Thanks for your reply. I can't replicate the problem with certain files. If I 
re-run the files, it won't 'crash' on the same file over and over. So, it's not 
the file which is breaking the server. It's some other variable (so, when I run 
the file with tike-app it works fine).

Could you indicate how I could configure the logging of the TIKA-server to a 
certain directory? Then I'm able to monitor the TIKA logs.

I'm aware of the spawnChild mode, however this is not ideal for my situation. 
My watchdog works fine and respawns TIKA straight away, but I would like to 
prevent it from crashing obviously

> Tika Server keeps crashing
> --------------------------
>
>                 Key: TIKA-2889
>                 URL: https://issues.apache.org/jira/browse/TIKA-2889
>             Project: Tika
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 1.18, 1.19, 1.19.1, 1.21
>         Environment: Both Ubuntu and Windows have the same bug/issue
>            Reporter: Thomas van Hesteren
>            Priority: Minor
>
> I have a document processor which sends documents to the Tika Server over 
> cUrl. However, the server crashes multiple times (not document specific). The 
> response I get from cUrl if it happens is as follows:
> Connection error: Couldn't connect to server
>  
> The Tika server is started when the script starts executing. For now, I fixed 
> the issue by making a watcher which restarts the tika server when it crashes. 
> It then processes a few other documents and crashes again (after a few 
> minutes, let's say 5 minutes tops).
>  
> Is there any possibility to catch the exception (if it throws any?)
>  
> A log which shows the crash of the server:
> 04-06-2019 15:49:25|Processing a file of: 52.3kB
> 04-06-2019 15:49:24|Processing a file of: 255.5kB
> 04-06-2019 15:49:24|Processing a file of: 241.6kB
> 04-06-2019 15:49:23|Processing a file of: 37.7kB
> 04-06-2019 15:49:22|Processing a file of: 1.27MB
> 04-06-2019 15:49:21|Processing a file of: 55.8kB
> 04-06-2019 15:49:17|Processing a file of: 114.5kB
> 04-06-2019 15:49:08|Server is not running. Restarting Server. Connection 
> error: Couldn't connect to server
> 04-06-2019 15:49:03|Processing a file of: 41.0kB
> 04-06-2019 15:49:00|Processing a file of: 38.0kB
> 04-06-2019 15:48:59|ProcesPsing a file of: 37.1kB
> 04-06-2019 15:48:59|Processing a file of: 60.2kB
> 04-06-2019 15:48:59|Processing a file of: 280.7kB
> 04-06-2019 15:48:59|Processing a file of: 3.30MB



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to