After changing these values, try to restart the application servers as instructed below.
Recommended values to give a try.
##### Data Source Properties #####
dataSource.maxWaitMillis=30000
dataSource.maxTotal=250
dataSource.minIdle=5
dataSource.minEvictableIdleTimeMillis=3000000
#dataSource.maxOpenPreparedStatements=-1
dataSource.maxTotal – this can be up to 500- for UI servers as per document reference:
IIQ Properties Settings - Compass
Controls the number of connections that can be attached to the database at one time; the default value is 50, though higher values are usually specified for production installations.
This setting is typically higher for UI servers than for task servers, and often ranges from 200-500. The max HTTP sessions in the application server also may need to be adjusted, and the database server must be configured to support all connections from all clients as well.
Installations taking advantage of the partitioning and parallelized aggregation features available in releases 6.2 and newer should consider increasing this number to 100 or 200 as a minimum for batch and task servers. Servers performing aggregations using partitioning use more database connections than servers performing single threaded aggregations.
Instructions:
- Stop Tomcat.
- Update
iiq.propertiesfile as recommended above. - Delete the
tempandworkfolders to clear the cache.
Note: You MUST stop the Tomcat server before deleting these folders content. While the temp and work folders in Tomcat can generally be deleted safely, stopping the server beforehand is crucial to prevent corruption or issues.
Please refer SailPoint best practices while updating these values.
- Start Tomcat.
Expected values in UI: from Object Browser – > Wrench Icon – Database
