[
https://issues.apache.org/jira/browse/JAMES-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2085.
---------------------------------
> Review logging in depth in James code
> -------------------------------------
>
> Key: JAMES-2085
> URL: https://issues.apache.org/jira/browse/JAMES-2085
> Project: James Server
> Issue Type: Improvement
> Reporter: Tellier Benoit
> Priority: Major
>
> We end up with routeing Exceptions in the IMAP code, and I would like to know
> the origin...
> We need to ensure uncaught exceptions are logged in error, with the stack
> trace. We can ensure that in:
> - ImapChannelUpstreamHandler::exceptionCaught
> - BasicChannelUpstreamHandler::exceptionCaught
> - ManageSieveChannelUpstreamHandler::exceptionCaught
> We also need to catch errors in Servlets in JMAP.
> Moreover, we have MailboxException (reported some unexpected error with the
> mailbox) logged as info or debug, providing having this information at the
> right level (warn or error).
> We can also imagine using IDE code inspections to detect some defects (empty
> catch blocks, TODO in catch blocks, see calls to logger without the root
> cause, see calls with wrong log level, etc...),
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
