roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kohei Nozaki (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ROL-2078) Hard to determinate the cause of mail provider setting error due to no stacktrace are logged
Date Fri, 01 May 2015 12:21:06 GMT
Kohei Nozaki created ROL-2078:
---------------------------------

             Summary: Hard to determinate the cause of mail provider setting error due to
no stacktrace are logged
                 Key: ROL-2078
                 URL: https://issues.apache.org/jira/browse/ROL-2078
             Project: Apache Roller
          Issue Type: Improvement
          Components: Installation & Configuration
    Affects Versions: 5.1.2
            Reporter: Kohei Nozaki
            Assignee: Roller Unassigned
            Priority: Minor


Currently, if Roller installation has any problem in mail provider setting, only following
message are logged:

{noformat}
WARN  2014-05-16 16:01:39,233 WebloggerStartup:prepare - Failed to setup mail provider, continuing
anyways.
Reason: ERROR connecting to mail server
{noformat}

That is because logging procedure simply discarded the stacktrace:

{code:java}
// setup mail provider, if configured
try {
    mailProvider = new MailProvider();
} catch(StartupException ex) {
    LOG.warn("Failed to setup mail provider, continuing anyways.\n"
            + "Reason: " + ex.getMessage());
}
{code}

I think it's not informative. recently I got stucked in mail provider configuration due to
this. in my case, the cause was missing intermediate SSL certification. I think it's very
difficult to determine that cause without stacktrace or message of parent exception in such
case.

I guess some Roller installation may not have mail provider intentionally, so adding stacktrace
logging in a verbose level than WARN seems reasonable.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message