Workaround

Restart the cluster to recalculate the Maximum Pool Size for all JDBC connection pools on all server instances.

Selecting individual JDBC connection pool names with individual Max Connections values instead of selecting * (applies to All Current and Future JDBC Connection Pools) can prevent this issue in real-time production environments.