You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Mike Rheinheimer (JIRA)" <ji...@apache.org> on 2010/07/23 16:29:07 UTC

[jira] Closed: (WINK-240) Change logging to be less noisy

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

Mike Rheinheimer closed WINK-240.
---------------------------------


Issue is resolved.  Closing per Bryant's approval to do so.

> Change logging to be less noisy
> -------------------------------
>
>                 Key: WINK-240
>                 URL: https://issues.apache.org/jira/browse/WINK-240
>             Project: Wink
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>             Fix For: 1.1
>
>
> Some users do not like the fact that we log every exception thrown (due to their use of exceptions in their method contracts for handling business logic).  Perhaps reducing the logging in RequestProcessor may be better:
> In RequestProcessor#logException(Throwable) replace statements like:
> {code}
> logger.error(String.format(messageFormat, exceptionName), t);
> {code}
> with:
> {code}
>             // don't log the whole call stack unless debugging
>             if (logger.isDebugEnabled()) {
>                 logger.debug(String.format(messageFormat, exceptionName), t);
>             } else {
>                 logger.info(String.format(messageFormat, exceptionName));
>             }
> {code}
> In a production environment, messages won't be logged but in development environments, a general message will be logged at info with the full  call stack at debug.

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