[
https://issues.apache.org/jira/browse/AVRO-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589700#comment-13589700
]
Doug Cutting commented on AVRO-1263:
------------------------------------
This sounds reasonable to me.
Perhaps, for back-compatibility, one could add setters to Responder that
determine the level these should be logged at, e.g.,
setUserErrorLogLevel(level) and setSystemErrorLogLevel(level). Unfortunately
slf4j doesn't have a log(level, message, ...) method, but we could work around
that, perhaps adding an 'enum Level {TRACE, DEBUG, INFO, WARN, ERROR}'
definition and 'static log(Logger, level, message, ...)' to Avro somewhere.
> Responder should not log SpecificExceptionBase in the same log level as
> RuntimeException
> ----------------------------------------------------------------------------------------
>
> Key: AVRO-1263
> URL: https://issues.apache.org/jira/browse/AVRO-1263
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.4
> Reporter: Tino Kissig
>
> It would be nice when only RuntimeExceptions or other exceptions to extending
> SpecificExceptionBase would be logged at WARN level.
> Our log file is flooded with Exceptions extending SpecificExceptionBase but
> we want to log them in a different way to the "unexpected" exceptions.
> Maybe SpecificExceptionBase exceptions could be logged in a lower log level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
