CAPC Dashboards timeout

Products

• CA Infrastructure Management
• CA Infrastructure Management
• CA Performance Management - Usage and Administration
• CA Performance Management - Data Polling

Issue/Introduction

Summary: 

Hot to increase the timeout queries on CAPC?

Background:  

Try to load a dashboard and get after a while a timeout error with the following message: “The server did not respond within the expected amount of time.”

Environment:  

PM 2.5 and 2.6

Instructions: 

Reporting Best Practices

What are some best practices for minimizing dashboard/report runtimes and database server load?

1. Choose the smallest timeframe possible that satisfies your requirements (i.e. 'Last Hour' or specific hour in the past)

2. Select the reporting group with the smallest membership possible that satisfies your requirements. Ask yourself, do you *really* need to run the dashboard against a collection with 10k items? Could you possibly run the dashboard against a smaller group?

3. When building custom dashboards, consider the number of queries issued by each dashboard “view”. For example, Top N multi-trend style reports typically issue 1 query to determine the Top N, then, separate queries for each of the N items returned. Given that the default for N is 10, a Top N style report leads to 11 queries.

Also you change the following:

1) Configure then the MAX memory for each process on CAPC box with the following values:

PC:
File: /opt/CA/PerformanceCenter/PC/conf/wrapper.conf
Variable:
From:
wrapper.java.maxmemory=1994
To:
wrapper.java.maxmemory=5120

DM :
File: /opt/CA/PerformanceCenter/DM/conf/wrapper.conf
Variable:
From:
wrapper.java.maxmemory=1994
To:
wrapper.java.maxmemory=6144

2) At general table for netqosportal database on CAPC box modify the following parameters:

Client.MaxWaitPeriodMs to 30000
Client.ServerExecutionTimeoutMs to 400000
Client.ServerExecutionTimeout to 400000

mysql
use netqosportal
select attribute,value from general where attribute="Client.MaxWaitPeriodMs";
update general set value=20000 where attribute="Client.MaxWaitPeriodMs";
select attribute,value from general where attribute="Client.MaxWaitPeriodMs";

select attribute,value from general where attribute="Client.ServerExecutionTimeoutMs";
update general set value=400000 where attribute="Client.ServerExecutionTimeoutMs";
select attribute,value from general where attribute="Client.ServerExecutionTimeoutMs";

select attribute,value from general where attribute="Client.ServerExecutionTimeout ";
update general set value=400000 where attribute="Client.ServerExecutionTimeout ";
select attribute,value from general where attribute="Client.ServerExecutionTimeout ";

b) Modify the rib-engine.properties file under
/opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF path

rib.engine.source_query_timeout_sec to 400

c) Modify the dm.properties file
under /opt/CA/PerformanceCenter/DM/webapps/dm/WEB-INF/ path
web.cxf.client.services_timeout to 400000

d) Modify the porrtal.console.properties file
under /opt/CA/PerformanceCenter/PC/webapps/pc/WEB-INF/cfg path
web.cxf.client.services_timeout to 400000

e) Then recycled all the services (PC/DM/EM/SSO/mysql)
Stop:
for I in `ls /etc/init.d/caperfcenter_*`;do $I stop; done
service mysql stop

Start:
service mysql start
for I in `ls /etc/init.d/caperfcenter_*`;do $I start; done

3) Configure then the MAX memory for DA and DC boxes, see Modify Maximum Memory Usage for Data Aggregator and Data Collector Components on site:
https://docops.ca.com/ca-performance-management/2-7/en/administrating/data-aggregator-administration/modify-maximum-memory-usage-for-data-aggregator-and-data-collector-components

 

Environment

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component: