Investigate improving DriverManager-based connection pooling

Description

Specifically in terms of concurrency, leveraging concurrent collections and executors.

Not sure this can/should become "supported for production use"; given the fact that we don't proxy the Connections, there is just too many situations we are unaware of where the Connection really ought to be destroyed rather than returned to the pool. All of this applies to the current DriverManagerConnectionProvider too though, so just talking about improving the concurrency design.

Environment

None

Assignee

Steve Ebersole

Reporter

Steve Ebersole

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Priority

Major
Configure