Parameters for JDBC Pooling

The following parameters are not displayed on the UI, but are used to tune JDBC pooling:

Maximum time to wait for connection to become available in millisecond.


This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/jdbc/help/integrating_jdbc/parameters_for_jdbc_pooling.html

This is another example of where the ISC documentation references XML, when the applications are Updated/stored in JSON.

Also, it would be good for ISC to note where these parameters should be added, either on the Application itself, or under the “connectorAttributes” parameter.

Here’s an example of the JSON Body that would add all of the variables.

[
  {
    "op": "add",
    "path": "/connectorAttributes/pool.minEvictIdle",
    "value": "600000"
  },
  {
    "op": "add",
    "path": "/connectorAttributes/pool.evictRuns",
    "value": "300000"
  },
  {
    "op": "add",
    "path": "/connectorAttributes/pool.maxActive",
    "value": "10"
  },
  {
    "op": "add",
    "path": "/connectorAttributes/pool.maxIdle",
    "value": "10"
  },
  {
    "op": "add",
    "path": "/connectorAttributes/pool.maxWait",
    "value": "60000"
  },
  {
    "op": "add",
    "path": "/connectorAttributes/pool.disablePooling",
    "value": "false"
  }
]

Additionally, the existing “minEvictIdle” value is set to 10, which would be 10ms, and I believe it was intended to be 10 minutes, or 600000ms, based on the values found here: JDBC connector - Configuring pool settings - Compass

Hi Geoff Milunich. Thanks for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-4265

The work for CONDOCS-4265 has been completed and the guide has been updated.