[
https://issues.apache.org/jira/browse/TIKA-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025345#comment-14025345
]
Tim Allison commented on TIKA-1323:
-----------------------------------
Great. Thank you, Sergey! I'll require that the option be set on the
commandline and the default will be the current behavior. I'll post a patch to
the review board by the end of the week or so.
Off topic, but related... I noticed that the server will keep running even if a
particular request causes an out of memory exception, other runtime exceptions
or even errors. This is an issue for another ticket, but before opening that
one, I wanted to confirm: does this make sense? Should the server keep running
even if there are serious exceptions or errors? I'd think we'd want it to
clean up, log everything and shut down, but I'd be interested in feedback.
If we do want the server to shutdown for serious exceptions/errors, then I'd
want to add a daemon that polls the server for status (are you still alive/how
many stale requests are you still processing?) and (re)restarts it if there are
problems.
Thoughts?
> Improve exception reporting in JAX-RS server
> --------------------------------------------
>
> Key: TIKA-1323
> URL: https://issues.apache.org/jira/browse/TIKA-1323
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Tim Allison
> Priority: Minor
>
> I'd like to use tika-server for TIKA-1302. As part of that, I'd like to
> record exception stacktraces per document. I see two options: transmit the
> info back to the client (assuming a doc didn't bring the server down :) )
> along with the current error code or log the document id and stacktrace via
> the server. Given my current design thoughts, I'd prefer the first option.
> Any objections or recommendations?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
