Rule Test button causes performance issues in RSA Identity Governance & Lifecycle
4 years ago
Originally Published: 2019-11-18
Article Number
000043617
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
 
Issue
Certain rule types such as the User Access rule type have a Test button that allows you to test the scope of the rule before running the actual rule (Rules > Definitions > {Rule Name} > Test.) In some situations performance issues may occur when testing rules.

The symptoms may be general slowness of the system or timeouts in the browser sessions.

The following messages may be logged in the aveksaServer.log:

06/17/2019 12:52:32.434 INFO (default task-194) [com.aveksa.server.db.persistence.PersistenceServiceProvider] executeCallableStatement
giving up after hitting SQLException:
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "AVUSER.RULE_PROCESS_PKG", line 1739
ORA-06512: at line 1 06/17/2019 12:52:32.435 WARN (default task-194) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 60, SQLState: 61000 06/17/2019 12:52:32.435 ERROR (default task-194) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper]
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "AVUSER.RULE_PROCESS_PKG", line 1739
ORA-06512: at line 1 06/17/2019 12:52:32.438 ERROR (default task-194) [com.aveksa.server.core.rule.RuleServiceProvider] java.sql.SQLException:
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "AVUSER.RULE_PROCESS_PKG", line 1739
ORA-06512: at line 1 Failed method=TestRun RuleService
 

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment.
 

Cause
The Test feature runs a query in the background.  When it is running, it displays the message:
 
Testing rule... this may take some time depending on the volume of data

while the query is running. The query will continue to run even if the browser is closed. If the operation does not complete within a reasonable time, users may be tempted to refresh the browser and hit the Test button again. If the Test is run multiple times, this may cause a performance issue or database deadlocks due to the same query running more than once. 

This is a known issue in the following versions and reported in engineering ticket ACM-98992:
  • RSA Identity Governance & Lifecycle 7.1.0
  • RSA Identity Governance & Lifecycle 7.1.1
 
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels:
  • RSA Identity Governance & Lifecycle 7.1.1 P04
  • RSA Identity Governance & Lifecycle 7.2

The fix prevents multiple rule test runs from running at the same time. In addition, rule test results are cleaned up after each test run which makes subsequent test runs much faster. 
 
Workaround
Avoid pressing the rule Test button more than once or testing the same rule before the previous test has completed.
 

Related Articles

Trending Articles

Don't see what you're looking for?