000028142 - How to increase connection pool settings for RSA Identity Management and Governance (IMG)

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028142
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.9.1
Platform: JBoss
O/S Version: SUSE Linux
Legacy Affected Versions: 4.1

1.  The following intermittent error is found in the "server.log" file either after certain UI operations or during login attempts where the login is unsuccessful:

2010-06-04 18:02:31,731 ERROR [org.hibernate.util.JDBCExceptionReporter]
No ManagedConnections available within configured blocking timeout ( 10000 [ms] ); -
nested throwable: (javax.resource.ResourceException:
No ManagedConnections available within configured blocking timeout ( 10000 [ms] ))


2.  The following is an example of a "workflow" stack trace error:

2010-06-04 18:57:44,238 ERROR [STDERR]
Jun 4, 2010 6:57:44 PM com.aveksa.gui.pages.portlet.myTasks.data.MyTasksStore getMyTasksCount
org.hibernate.exception.GenericJDBCException: Cannot open connection
at com.aveksa.server.workflow.WorkflowServiceProvider.getWorkflowWorkItemsCount(WorkflowServiceProvider.java:2092)


This error can occur when the system does not have the correct connection pool settings for the JDBC datasources found in the "aveksa-ds.xml" file located in /home/oracle/jboss/server/default/deploy.

For each of the <datasources>, the <max-pool-size> is 50 by default.  For customers with a high user load/volume, this max value may be increased for each of the datasource entries in the aveksa-ds.xml file.  For example: 


Once this file has been modified, stop and restart the Aveksa Services:

acm restart

       1.  For workflow performance issues the following is the only datasource that should be modified in the aveksa-ds.xml file:


       2.  As a first step increase it to:


       3.  Restart the acm server for the changes to take effect:
acm restart
NotesPrevious KB ID: KB-1371