[
https://issues.apache.org/jira/browse/DIRMINA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512890
]
Trustin Lee commented on DIRMINA-313:
-------------------------------------
Sorry for getting back to this issue very late, but should we log
exceptionCaught at INFO level? I thought it was supposed to be logged at WARN
level. I recently had some trouble finding caught exceptions because of the
logging level. WDYT?
> LoggingFilter logs exceptionCaught events on error level but uses
> isInfoEnabled in the if-statement
> ---------------------------------------------------------------------------------------------------
>
> Key: DIRMINA-313
> URL: https://issues.apache.org/jira/browse/DIRMINA-313
> Project: MINA
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Niklas Therning
> Assignee: Niklas Therning
> Priority: Minor
> Fix For: 1.0.1
>
>
> Here's the relevant piece of code:
> if( SessionLog.isInfoEnabled( session ) )
> {
> SessionLog.error( session, "EXCEPTION:", cause );
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
