How to increase the max-pool-size for the Workpoint data source (WPDS) in RSA Identity Governance & Lifecycle

[#1]

Article Number

000030757

Applies To

RSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 6.9.1, 7.0.x, 7.1.0
Platform: WildFly

Issue

NOTE: This RSA Knowledge Base Article applies to RSA Identity Governance & Lifecycle versions 7.1.0 and earlier.

The max-pool-size connection setting for the Workpoint data source (WPDS) may be set to 90, which is too low for heavy workflow usage. Engineering recommends a minimum setting of 150. On a system with heavy workflow usage, this value may need to be increased above 150.

Examples of errors that indicate connections need to be increased are as follows:

1. These errors are often noticed in the server.log file ($AVEKSA_HOME/wildfly/standalone/log/server.log), if login attempts fail.

==========
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. In the WorkPoint.log file ($AVEKSA_HOME/wildfly/standalone/log/WorkPoint.log) the following messages may show:

==========
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

SEVERE:
com.aveksa.server.workflow.WorkflowServiceException:
com.aveksa.server.db.PersistenceException:
org.hibernate.exception.GenericJDBCException: Cannot open connection
at com.aveksa.server.workflow.WorkflowServiceProvider.getWorkflowWorkItemsCount
(WorkflowServiceProvider.java:2092)
==========

 

Resolution

Steps to modify the Workpoint Data Source (WPDS) max-pool-size

On a standalone (non-clustered) system:

1. Log in as user oracle.
2. Edit the aveksa-standalone-full.xml file.

$ cd home/oracle/wildfly/standalone/configuration
$ vi aveksa-standalone-full.xml

3. Change <max-pool-size>90</max-pool-size> to <max-pool-size>150</max-pool-size>.

<xa-datasource jndi-name="java:/jdbc/WPDS" pool-name="WPDS" enabled="true" use-java-context="true" use-ccm="true">
    <xa-datasource-property name="URL">
        jdbc:oracle:thin:@//localhost:1555/AVDB
    </xa-datasource-property>
    <driver>OracleXADriver</driver>
    <xa-pool>
        <min-pool-size>10</min-pool-size>
        <max-pool-size>150</max-pool-size>

4. Restart RSA Identity Governance & Lifecycle.

$ acm restart

On a cluster:

1. Log in to the domain controller as user oracle.
2. Edit the domain.xml file.

$ cd home/oracle/wildfly/domain/configuration
$ vi domain.xml

3. Change <max-pool-size>90</max-pool-size> to <max-pool-size>150</max-pool-size>.

<xa-datasource jndi-name="java:/jdbc/WPDS" pool-name="WPDS" enabled="true" use-java-context="true" use-ccm="true">
    <xa-datasource-property name="URL">
        jdbc:oracle:thin:@//localhost:1555/AVDB
    </xa-datasource-property>
    <driver>OracleXADriver</driver>
    <xa-pool>
        <min-pool-size>10</min-pool-size>
        <max-pool-size>150</max-pool-size>

4. Restart all nodes of the cluster.

SuSE 11 commands

service aveksa_cluster stop
service aveksa_cluster start

SuSE 12 commands

systemctl stop aveksa_cluster
systemctl start aveksa_cluster

Notes

This setting may also need to be modified in RSA Identity Governance & Lifecycle 6.9.1:

1. Login as user oracle.
2. Edit the aveksa-ds.xml file.

$ cd /home/oracle/jboss/server/default/deploy
$ vi aveksa-ds.xml

3. Change <max-pool-size>90</max-pool-size> to <max-pool-size>150</max-pool-size>:

<xa-datasource>
        <jndi-name>jdbc/WPDS</jndi-name>
        <track-connection-by-tx/>
        <isSameRM-override-value>false</isSameRM-override-value>
        <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
        <xa-datasource-property name="URL">jdbc:oracle:thin:@//localhost:1555/avdb</xa-datasource-property>

        <!-- Determines whether database exceptions are fatal. Our custom exception sorter delegates 
        to org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter, 
        but then marks certain exceptions "fatal" which the default sorter determind to be "non-fatal". -->
        <exception-sorter-class-name>com.aveksa.jdbc.OracleExceptionSorter</exception-sorter-class-name>

        <no-tx-separate-pools/>
        <max-pool-size>150</max-pool-size>

4. Restart RSA Identity Governance & Lifecycle 

$ acm restart