We have one DB2 database in Production (One instance). We are dealing with a cluster with two IS servers and each WM IS server is configured with a single JDBC connection pool to this DB2 database with a maximum of 150 connections each. Multiple webmethods projects/apps/services use this connection pool to connect to DB2 database. But during Production outage (ran out of available connections in the connection pool) the difficulty was isolating the specific services consuming the connections in the pool. So all the services hosted on the servers and using this connection pool were impacted.
What is the best pratice to avoid this scenario? Do we create multiple JDBC Connection pools? At what level? One pool per service? Or one pool per Project/Application? We have both non-enterprise project specific and enterprise (shared services) services.
Does having one JDBC connection pool v/s many pools for the DB2 database per IS server save WM IS server resources? At what point does having multiple JDBC connection pools to the same db2 database become a Administrative nightmare?
At the same time how do we achieve service isolation such that if there is a problem with connections in one pool, all the other applications are not impacted. I’m looking for best pratices. Any ideas are welcome. Thanks much.