Github user colindean commented on the issue:
https://github.com/apache/nifi/pull/3133
> What if you exposed the number of active and idle connections in the
connection pool as properties on the DBCPConnectionPool? These are available by
calling getNumActive() and getNumIdle(). Or you could call listAllObjects() and
get back the full pool on the dataSource object.
I started down this track but I couldn't actually seem to trigger idle
within a reasonable test setup. I can't for the life of me tell what actually
makes a connection go idle, only really what removes it _when_ it's idle.
Thoughts on how to proceed?
---
