[
https://issues.apache.org/jira/browse/TIKA-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857834#comment-16857834
]
Thomas van Hesteren commented on TIKA-2889:
-------------------------------------------
I ran the code with debugging cUrl which shows the following (broken pipe.
Presumably because of Tika Server crashing?):
06-06-2019 18:07:10|Curl Verbose|Send header => Accept: application/json
06-06-2019 18:07:10|Curl Verbose|Send header => Host: localhost:12345
06-06-2019 18:07:10|Curl Verbose|Send header => PUT /rmeta/text HTTP/1.1
06-06-2019 18:07:10|Curl Verbose|Send header => Connected to localhost
(127.0.0.1) port 12345 (#0)
06-06-2019 18:07:10|CurlVerbose|Info => Connected to localhost (127.0.0.1) port
12345 (#0)
06-06-2019 18:07:10|Curl Verbose|Send header => TCP_NODELAY set
06-06-2019 18:07:10|CurlVerbose|Info => TCP_NODELAY set
06-06-2019 18:07:10|Curl Verbose|Send header => Trying 127.0.0.1...
06-06-2019 18:07:10|CurlVerbose|Info => Trying 127.0.0.1...
06-06-2019 18:07:10|Curl Verbose|Send header => connect to ::1 port 12345
failed: Connection refused
06-06-2019 18:07:10|CurlVerbose|Info => connect to ::1 port 12345 failed:
Connection refused
06-06-2019 18:07:10|Curl Verbose|Send header => TCP_NODELAY set
06-06-2019 18:07:10|CurlVerbose|Info => TCP_NODELAY set
06-06-2019 18:07:10|Curl Verbose|Send header => Trying ::1...
06-06-2019 18:07:10|CurlVerbose|Info => Trying ::1...
*LIFE CHECKER LOG 06-06-2019 18:07:07|Warning|Tika is not running. Restarting
Tika. Connection error: Failed sending data to the peer*
06-06-2019 18:07:07|Curl Verbose|Send header => Closing connection 0
06-06-2019 18:07:07|CurlVerbose|Info => Closing connection 0
06-06-2019 18:07:07|Curl Verbose|Send header => stopped the pause stream!
06-06-2019 18:07:07|CurlVerbose|Info => stopped the pause stream!
06-06-2019 18:07:07|Curl Verbose|Send header => Send failure: Broken pipe
06-06-2019 18:07:07|CurlVerbose|Info => Send failure: Broken pipe
06-06-2019 18:07:07|Curl Verbose|Send data => h8OaQhcHxnhjVhvYS5GfW
06-06-2019 18:07:07|Curl Verbose|Send data =>
zSr+P339NJSxziAoA+Vx5KydHctZBB19Gx5shmMyyzDbcHX1lQ51X5L0Ws8CYVev0P/9QL3q2Ouu
06-06-2019 18:07:07|Curl Verbose|Send data =>
+7CWUcTK0ZZ+qwNNHR73Yus96y51EZD/DjUqOO72JkMnF0O8Vo0Y2B4xU07HSm43F1MgH+nr+BeY
06-06-2019 18:07:07|Curl Verbose|Send data =>
azR6nBXEveddt/Lflp2fwCWB2mJGW5VUjBjgLzGPjC7h6A8ekfIxsJDxZ4n8jsfC4ZsE1HR2kcaN
................ Lot's of send data entries ................
> 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
> Attachments: log4j.xml, tika-2.log, tika-server-everything-2.log,
> tika-server-everything.log, tika-server-everything.log,
> tika-server-everything.log, tika.log, tika.log
>
>
> 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)
