Multiple AES features unusable due to timeout
SummaryUsers Autonomic Event Services (AES) 7.1.7 production server on Pega 7.1.7, is currently monitoring 12 PRPC production and pre-production clusters with a total of 38 PRPC nodes.
Some of the production clusters have several hundreds of users in parallel. This produces a large number of alerts (more than 2.3 million) in the AES database table PEGAAM_ALERT.
Due to this large number of alerts several queries to retrieve AES report data exceed the current built-in limit of 30 seconds.
This in turn leads to the problem that several AES features are unusable.
For some reports the error message "Retrieving the report data exceeded the limit of 30 seconds." is shown in the AES GUI.
Some features, example "Tools - System Connectivity" or the Dashboards, just return no data or maybe incomplete data without any error message in the AES GUI.
For cases like these there is an error message "java.sql.SQLTimeoutException / ORA-01013: user requested cancel of current operation" in the AES log files.
Users are looking for a central AES configuration ( a dynamic system setting) that allows a Pega AES customer to increase this timeout in a central place via configuration without modifying a large number of AES built-in reports and other GUI elements.
Error Messagesjava.sql.SQLTimeoutException / ORA-01013: user requested cancel of current operation
Steps to ReproduceNot Applicable
Root CauseThere is already a way to set the default timeout for all reports in one place, this is done via some system settings the Out-of-the-box (OOTB) default settings can be viewed at the following landing page:
Designer Studio > Reporting > Settings > Settings
ResolutionThe way to increase the timeout for all reports is to open the following system settings:Save this system setting to the own ruleset that is available to the operators who will access the reports, then change the timeout to reflect the timeout that is required.
Published March 3, 2017 - Updated March 22, 2017