You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2017/07/01 21:39:01 UTC
[jira] [Updated] (ROL-2078) Hard to determinate the cause of mail
provider setting error due to no stacktrace are logged
[ 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)