Manage JDBC Connections Maximum Pool Size in Policy Manager
Article ID: 223256
Updated On:
Products
Issue/Introduction
Questions about Manage JDBC Connections in Policy Manager.
Are requests beyond the Maximum Pool Size immediately failed (or failed) rather than waiting for resources to be created in the connection Pool?
Environment
Release : 9.4
Component :
Resolution
It depends on the jdbc driver.
For the default l7tech jdbc drivers (Datadirect jdbc drivers), the default behaviour is,
The number of active connections can exceed the maximum pool size, but the number of idle connections for each user in the pool cannot exceed this limit. If a user requests a connection and an idle connection is unavailable, the Pool Manager creates a new connection for that user. When the connection is no longer needed, it is returned to the pool. If the number of idle connections exceeds the maximum pool size, the Pool Manager closes idle connections to enforce the pool size limit.
Feedback
