Configure the Database Connection Pool - User Data Repository

Relational databases typically use a pool of connections to make it more efficient for applications to connect to the database. With a connection pool, the RDBMS maintains a specific number of open connections for each given connection configuration. When the database receives a connection request, it allocates a connection from the pool, rather than opening a new connection. 

When you set up the User Data Repository and Job Queue Manager to connect to a relational database, it is important to make sure that the connection pool settings configured in your database are sufficient to support all the connections from

Step 1 - Check Configured Connection Settings

Calculate the total maximum number of connections configured for the following features:

FeatureSettingDefined In
SuperWEB2 User Data Repository

maxTotal

The  Resource  settings in  <tomcat_home>\conf\server.xml
SuperWEB2 Job Queue Manager

maxTotal

The  Resource  settings in  <tomcat_home>\conf\server.xml
SuperADMIN (when storing user data in the RDBMS)eclipselink.jdbc.read-connections.max and eclipselink.jdbc.write-connections.maxThe relevant database configuration properties file in the SuperADMIN server configuration directory (typically C:\ProgramData\STR\SuperADMIN\server\config)
Any other processesCheck the settings for any other processes running on your network that connect to the same RDBMS

Step 2 - Configure the Connection Pool in the RDBMS

Configure the connection pool settings in the RDBMS so that there are enough connections to support the figure you reached in step 1. Refer to your RDBMS documentation for help with this step.