roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Johnson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ROL-2078) Hard to determinate the cause of mail provider setting error due to no stacktrace are logged
Date Sat, 01 Jul 2017 21:39:01 GMT

     [ https://issues.apache.org/jira/browse/ROL-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Johnson updated ROL-2078:
-------------------------------
    Fix Version/s: 5.2.0

> 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
>             Fix For: 5.2.0
>
>         Attachments: ROL-2078.patch
>
>
> 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.4.14#64029)

Mime
View raw message