Long delay in listDomains API response

Hi, We have upgraded ACS from 4.2 to 4.8.1.1. We noted that a "listDomains" API call from our billing system took 21 seconds for our CloudStack to reply, resulting in time-out. 2016-11-06 03:40:42,891 DEBUG [c.c.a.ApiServlet] (http-8080-2:ctx-faa0bcbd) (logid:86b581fc) ===START=== X.X.X.X

Re: Long delay in listDomains API response

You will probably need to enable TRACE logging and see what SQL query took long time to execute. On 11/5/16, 1:21 PM, "Cloud List" wrote: Hi, We have upgraded ACS from 4.2 to 4.8.1.1. We noted that a "listDomains" API call from our billing system took 21

[GitHub] cloudstack issue #1578: CLOUDSTACK-9401 : Support for Internal DNS in Nuage ...

Github user prashanthvarma commented on the issue: https://github.com/apache/cloudstack/pull/1578 @jburwell @rhtyd We have briefly investigated the above test failures, and here are our findings: 1) No single test is failing across all the environments, and this PR doesn't

Re: Long delay in listDomains API response

Thanks Sergey for your assistance. I have enabled the TRACE logs as requested. After the listDomains API call, I see a lot of DB connections being created to the database, preparing SELECT statements and then immediately being closed thereafter. This happens many many times in the loop in the

Re: Long delay in listDomains API response

Hi Sergey, Thanks for your reply. May I know logging for which class I need to modify to TRACE? Is it for the c.c.a.ApiServelet class? Not too sure what does the c.c.a stands for -- how do I check that? So I can put the correct full name of the class category on

Re: Long delay in listDomains API response

Please change DEBUG to TRACE for the following classes so they look like below. You don’t need to restart Cloudstack since it will dynamically switch log level. Once switched it will start generating enormous amount of logging so once you capture the slowness switch it back to DEBUG.