Ah, you are referring to a JDBC/DataSource connection pool.
That's very, very, specific. (You could have also be referring to HTTP/2 channel connection pools, or HttpClient connection pools, for example)
JDBC/DataSource connection pooling is not handled by Jetty.
This decisions was made after analyzing the popular DataSource options out there.
What we found was that many existing DataSource implementations can do their own Connection Pooling (often far better than a generic solution)
And for those DataSource implementations that don't have a built-in connection pooling, there are many excellent, and existing DataSource pooling solutions for those.
See things like:
- BoneCP
- HikariCP
- c3p0
- commons-dbcp
Since you seem to be using Oracle, I would advise looking into the various Oracle JDBC driver built-in options for connection pooling.
And you have a lot of choices within Oracle, as there's got to be about a dozen different DataSource driver options for you (depending on your oracle server and oracle client setups)