[
https://issues.apache.org/jira/browse/TIKA-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zac Jacobson updated TIKA-3680:
-------------------------------
Affects Version/s: 2.3.0
> Use logging instead of e.printStackTrace()
> ------------------------------------------
>
> Key: TIKA-3680
> URL: https://issues.apache.org/jira/browse/TIKA-3680
> Project: Tika
> Issue Type: Improvement
> Components: server
> Affects Versions: 1.28, 2.3.0
> Reporter: Zac Jacobson
> Priority: Major
>
> When running tika-server, by default response messages are sent to stdout,
> and logging is sent to stderr. But the project also calls e.printStackTrace()
> in a number of places which dumps stack traces directly to stderr, and they
> are not decorated with the configured logging formatters.
> This makes managing tika's logs on a centralized log host such as ELK
> cumbersome.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
