[
https://issues.apache.org/jira/browse/CLOUDSTACK-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13576053#comment-13576053
]
ASF subversion and git services commented on CLOUDSTACK-1124:
-------------------------------------------------------------
Commit 1e8648c92de9df281aaabc5067d6d1d61be3a4a3 in branch refs/heads/master
from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=1e8648c ]
CLOUDSTACK-1124 [EC2 Query API] Improve the logging. Having empty response
objects is harmless to functionality
This is observed in the awsapi.log for all Describe* EC2 commands when the
response object returned by CS has no elements. But with EC2DescribeImages
command it is always observed. This is because every time DescribeImage is
fired, we call CS listTemplates command multiple times, each time setting a
different value for the templateFilter parameter (e.g. featured, executable,
community etc.). And for some of these CS calls made we obtain am empty
response and hence the message in the logs.
> Improve the logging. Having empty response objects is harmless to
> functionality
> --------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1124
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1124
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: AWSAPI
> Affects Versions: 4.0.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
>
> Though there is no functional impact, log message is displayed as null when
> there response is empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
