In a Remote Oracle database setup, there is a chance that the remote Oracle connections could get dropped for some reason. It could be done by a firewall or some other networking infrastructure that might think a connection is idle while a stored procedure (e.g. a Collection) is taking some time to finish and drop the connection. When the network connection for an Oracle session gets dropped, the client (the RSA Identity Governance & Lifecycle application in this case) does not get notified of the event, so it keeps waiting indefinitely for the response to arrive from the server. In order to prevent such cases and be able to detect connection interruptions, ConnectionPools (in various Application Servers) have configuration options for validating existing database connections.
In every Application Server's Connection Pool configuration there is an option to periodically test the connection and close it when it goes down. Starting in RSA Identity Governance & Lifecycle 7.1.1 these settings are enabled by default. Prior to 7.1.1 to modify the default WildFly settings to properly detect database connectivity issues, the $AVEKSA_HOME/wildfly/standalone/configuration/aveksa-standalone-full.xml (or $AVEKSA_HOME/wildfly/domain/configuration/domain.xml file in a cluster) file can be modified as shown below. Make these modifications for every <datasource> and <xa-datasource> section in the configuration file. These modifications enable a check on the database connections every 30 seconds.