james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tellier Benoit (JIRA)" <server-...@james.apache.org>
Subject [jira] [Created] (JAMES-2085) Review logging in depth in James code
Date Mon, 03 Jul 2017 11:39:00 GMT
Tellier Benoit created JAMES-2085:

             Summary: 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

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

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message