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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
