[
https://issues.apache.org/jira/browse/WINK-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790257#action_12790257
]
Hudson commented on WINK-240:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #248 (See
[http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/248/])
Reduce logging in error path case
Stacktraces/exception objects still avaialble
in debug mode but in normal mode a simpler
info message is logged. Exception still thrown
to container and in Geronim/Tomcat this
means the stack trace is still printed out to
the container log outside of Wink.
See []
> 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
> 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.
