Uploaded image for project: 'Tika'
  1. Tika
  2. TIKA-3680

Use logging instead of e.printStackTrace()

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.28, 2.3.0
    • 2.4.0
    • server
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            zac-jacobson Zac Jacobson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment