JDBC Cluster Properties
The following cluster properties are used in JDBC connections and JDBC queries. See related topics:
gateway83
The following cluster properties are used in JDBC connections and JDBC queries. See related topics:
Property | Description |
|---|---|
jdbcConnection.driverClass. defaultList | Lists upported database driver classes for JDBC connections. Enter each driver class on a new line. Default: com.mysql.jdbc.Driver com.l7tech.jdbc.mysql.MySQLDriver com.l7tech.jdbc.db2.DB2Driver com.l7tech.jdbc.oracle.OracleDriver com.l7tech.jdbc.sqlserver.SQLServerDriver Before modifying the default list of supported driver classes, see Understanding the Driver Classes in JDBC Connection Properties. |
jdbcConnection.pooling. maxPoolSize.defaultValue | Maximum number of connections maintained by a pool. Used in the JDBC Connection Properties. Default: 15 |
jdbcConnection.pooling. minPoolSize.defaultValue | Minimum number of connections maintained by a pool. Used in the JDBC Connection Properties. Default: 3 |
jdbcQuery.maxBlobSizeOut | Maximum size for a BLOB output variable form a Procedure or Function call. Enter zero for no maximum size. Default: 10485760 (bytes = 10 MB) |
jdbcQuery.maxClobSizeOut | Maximum size for a CLOB output variable from a Procedure or Function call. Enter zero for no maximum size. Default: 10485760 (bytes = 10 MB) |
jdbcQuery.maxRecords. defaultValue | The default maximum number of records to return from querying a JDBC connection. Used in the Perform JDBC Query assertion. Default: 10 |
jdbcQueryManager. cacheCleanUpInterval | Enable cache clean up of cached exceptions. Enter zero to disable cache cleanup. Default: 60000 (milliseconds) |
jdbcQueryManager. cacheKeyNoUsageExpiration | Maximum expiration for a managed meta data cache key. The default is 31 days. Set to zero for no expiration. Default: 2678400 (seconds) |
jdbcQueryManager. cacheMetaData.enable | Controls the caching of procedure or function metadata. If enabled, lazy caching happens as meta data is downloaded. Connections referenced via a context variable always requires lazy caching. Value is a Boolean. Default: true This property does not affect existing cached data and does not stop background tasks from checking cached data. This allows caching to be turned on and off without causing all existing cached data to be lost. For details, see "Caching Metadata" in the Perform JDBC Query assertion |
jdbcQueryManager. cacheMetaDataTask.enable | Controls the background task to cache procedure or function meta data. Value is a Boolean. Default: true |
jdbcQueryManager. cacheRefreshInterval | Refresh interval when background task updates meta data cache. The default is 10 minutes. Set to zero for no refresh. Default: 600000 (milliseconds) |
jdbcQueryManager. cacheStaleTimeout | Maximum cache age of meta data. Any cached meta data older than this value is cleared from the cache. Set to zero for no timeout. Default: 1800 (seconds) |
jdbcQueryManager. cacheTaskStatementTimeout | Maximum statement query time allowed for queries from the meta data cache background task. Set to zero to use the Gateway-wide timeout. Default: 120 (seconds)This property is ignored if it is larger than the API Gateway -wide timeout defined byqueryManager.maxGatewayStatementTimeout. |
jdbcQueryManager. maxGatewayStatementTimeout | Maximum statement query time on the API Gateway . This is a API Gateway -wide timeout. The minimum is 1 second.Default: 300 (seconds) |
jdbcQueryManager. minCacheConcurrency | Number of threads used by the background cache meta data task. Maximum value is 200, minimum value is 1. Default: 10 When changing the value of this property, consider the number of JDBC connections in use for procedures and functions on the API Gateway . And how this background task affects available connections for those JDBC connections. For example, if all JDBC connections in use are for a single database, then its pool size needs to accommodate the number of connections this background metadata task creates. |