JDBC Connection pooling is a mechanism that limits runaway use of server-side resources. JDBC connections are reused after being creating, saving the time to recreate them.
When the server requests a JDBC connection, one is created; once it's no longer needed it's released and can be reused. The CLM system manages the JDBC connection pool.
We can track the JDBC connection pool usage through the RepoDebug service.
- Login to the CCM admin page and navigate to the Advanced Properties.
- Search for the Property: 'Enable repodebug service' and change the default 'false' to 'true'. Save it.
- Now, navigate to the repodebug services:
- Click on the JMX management beans service (mxBeans) REST service.
- Search for 'JDBC connection pool' and Click on the service which navigate to the below URL:
- The 'CurrentPoolSize' key is the one which will show the usage out of the Max entries allocated.