cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10315) Inconsistent debugging info in catch block
Date Fri, 06 Apr 2018 21:21:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-10315:

blueorangutan commented on issue #2547: CLOUDSTACK-10315 Inconsistent debugging info in catch
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1883

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Inconsistent debugging info in catch block
> ------------------------------------------
>                 Key: CLOUDSTACK-10315
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Zhenhao Li
>            Priority: Minor
>              Labels: easyfix
>         Attachments: image-2018-03-05-09-59-19-369.png, image-2018-03-05-10-14-00-552.png,
image-2018-03-05-10-14-25-802.png, image-2018-03-26-17-45-44-489.png
> We found that some logging statements have same log message, but one of them has stack
trace info, the other one of them doesn't have. Maybe a possible reason is that they are code
clone, developers changed one of them(add stack trace info) but forgot to change the other
one. Here's the details of those logging statements we found:
>  1.*"Moving on to the next host because " + h.toString() + " is unavailable"*,
> There are two identical log messages in these two places, the previous one logged stack
> !image-2018-03-26-17-45-44-489.png!
> But the latter one did not:
> !image-2018-03-05-09-59-19-369.png!
> We can see that they are in different type of catch block, but when checking the logs
they generated, maybe it's impossible to know the difference of them without stack trace.
So maybe the stack traces info should also be added here?
> 2.*"Network rule Conflict"*
> _org.apache.cloudstack.api.command.user.firewall.CreatePortForwardingRuleCmd.*create()*,_
> _org.apache.cloudstack.api.command.user.firewall.CreateFirewallRuleCmd.*create()*_
> The previous one has these two logging statements:
>"Network rule conflict: ", ex);
> s_logger.trace("Network Rule Conflict: ", ex);
> Comparing to the latter one which contains:
>"Network rule conflict: " + ex.getMessage());
> s_logger.trace("Network Rule Conflict: ", ex);
> Maybe it's better to have consistent exception handling here?

This message was sent by Atlassian JIRA

View raw message