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

Hudson commented on TIKA-1323:
------------------------------

SUCCESS: Integrated in tika-trunk-jdk1.7 #599 (See 
[https://builds.apache.org/job/tika-trunk-jdk1.7/599/])
TIKA-1323: flush writer when printing stack trace (tallison: 
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1670807)
* 
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TikaServerParseExceptionMapper.java


> 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.3.4#6332)

Reply via email to