vCenter Server JDBC Connection Pool Max Size Configuration Lacks Upper Bound Enforcement

Goal: Ensure that the JDBC connection pool size for vCenter Server’s embedded vPostgres database remains within safe limits to prevent intermittent connection pool exhaustion and associated API or UI timeouts.

Constraint: The db.connection.pool.maxSize setting has no enforced upper bound, allowing values that may exceed PostgreSQL’s max_connections or the host’s file descriptor limit, which can destabilize vCenter or cause connection refusals.

• What mechanism can be used to enforce an upper bound on db.connection.pool.maxSize that aligns with PostgreSQL’s max_connections and OS limits?
• How should administrators calculate a safe maximum pool size given their specific PostgreSQL configuration and system resources?
• Is there a supported way to monitor JDBC pool utilization in real time to detect approaching exhaustion without relying solely on log messages?