After upgrading to dSeries 25.1, the server repeatedly encounters connection errors to the PostgreSQL database and restarts the server process. The following error is observed in the desktop client or logs:
FATAL: sorry, too many clients already (SQL state 53300)Product: Workload Automation DE (dSeries)
Version: ALL
Database: PostgreSQL
The issue is caused by the database connection pool reaching its limit. In dSeries 25.1, the database.maxconnections.in.pool parameter defaults to 100 if not explicitly defined in the db.properties file. If the PostgreSQL max_connections setting is also set to 100, the server quickly exhausts available connections, leaving no room for administrative tools, reporting, or desktop client connections.
To resolve this issue, increase the maximum number of connections allowed in the dSeries connection pool and ensure the database itself is configured to support the higher limit.
setdbparm database.maxconnections.in.pool
Enter new max connections in pool: 250
max_connections parameter is set higher than the dSeries pool size to accommodate additional overhead (e.g., administrative tools, HA nodes).db.properties file. You should see the following entry:# Added by Managerdatabase.maxconnections.in.pool=250For more details on the setdbparm utility, refer to the documentation: Configuring the Database Connection