[jira] Updated: (SHINDIG-1418) Write detailed logging to debug, not warning or info

["Richard Atkins (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SHINDIG-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Atkins updated SHINDIG-1418:
------------------------------------

    Attachment: debug-detail-logging.patch

Attached is a patch against trunk that will address this issue. This will probably also work against most of the version branches, although I haven't tried that.

> Write detailed logging to debug, not warning or info
> ----------------------------------------------------
>
>                 Key: SHINDIG-1418
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1418
>             Project: Shindig
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Richard Atkins
>         Attachments: debug-detail-logging.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> When shindig gets an error (4xx or 5xx) from the server while fetching data, shindig will generate a very large log message containing the full conversation trace leading up to the error. On systems where these errors are triggered every time someone views a page, this can quickly fill the error log. Shindig should log a brief summary of the warning (or info) to that logger, and only log the details of the connection error to the debug logger.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.