Unanswered: Recommended settings for connection pooling in DB2.
Users of our application are getting the below errror:
Error:ERROR  [IBM][CLI Driver] SQL1226N The maximum number of client connections are already started. SQLSTATE=57030 ERROR  [IBM][CLI Driver] SQL1226N The maximum number of client connections are already started.
When I tried to research it found out that the error is caused because of connection pooling and following settings can be changed in DB2 to troubleshoot the error:
There is not a "one size fits all" setting.
It requires to be tuned appropriately for your needs and your hardware resources.
Post your DB2-server version+fixpack, and the operating-system-name.
Post the existing values of those parameters you mention.
Post whether the connections originate with an application-server (e.g. Websphere or similar app server), or whether the connections are from ODBC applications/JDBC applications on individual workstations. Application-Servers usually have their own pooling.
Additionally, enterprise databases often use WLM, and configure it to force off idle connections after a configurable time . Even without WLM you can arrange for stale connections to be cleaned.