Monitoring for DBCP database?

Question

The huge webapp in my Tomcat sometimes starts using too many DBCP connections, which leads to problems.
To explore, I want to know at every moment in time that the thread / method supports pooling. No need to be in real time, post-mortem analysis is in order.

I searched for such a DBCP monitoring tool, in vain, so I'm going to write my own. (if there is any interest, I can make it open source)

Here is my plan:

• Change PoolingDataSource.getConnection to log in DBCP+1 <thread-id> "
• Change DelegatingConnection.close to register DBCP-1 <thread-id> "
• Write a small script to create this simple CSV for visualization:

QUESTION:
Is any Commons-DBCP 1.4 concept missing that makes the idea invalid?
Or am I reinventing the wheel?

Answer 1

There was no such tool, so I created it:

https://github.com/nicolas-raoul/Commons-DBCP-monitoring

It controls the use of the Commons database (using / waiting for a connection) and allows you to create such charts:

I asked if my assumptions on the Commons DBCP mailing list are valid.