• SecurID Governance & Lifecycle 7.5.2

Customers may experience various timeouts when attempting to edit or test collectors.

This issue is most common with JDBC collectors but affects all collector types.  The exact nature of the failure depends on what is being edited in the collector and what type of environment is involved.

Timeout after clicking the "Test Connection" button on the connection screen:

Timeout on Mapping for account collector attributes page when loading Schemas:

Timeout when clicking "Test" on Mapping for account attributes page:

The timeouts may cause the browser session to pause for an extended amount of time and then continue or fail.  Depending on the delay the failure may be in the browser, the Wildfly application server, or the firewall or load balancer.  The error message depends on what times out first but always indicates the page cannot be displayed.

Relevant log entry in aveksaServer.log:

09/14/2023 12:39:16.376 ERROR (default task-9022) [com.aveksa.gui.pages.admin.collector.utils.CollectorUtils$2] 
com.aveksa.server.runtime.ServerException: Request timed out

When editing (or moving through the collector editor pages) the collector periodically makes a connection to the external endpoint to retrieve information including certificates and schema from the database (or LDAP).  These queries create a JDBC connection on the agent (local or remote) where the collector is configured.

Delays in processing these external JDBC or LDAP requests occasionally can lead to a deadlock condition in the messaging between the server and the agent.

This issue is resolved in the following versions which include improvements in the message handling between the server and the agent:

• SecurID Governance & Lifecycle 7.5.2 P08
• RSA Governance & Lifecycle 8.0.0