We're observing a strange behaviour on one of our WebLogic instances. A data source is configured with initial and maximum capacities of 50, and yet when monitoring the data source, we're seeing an active connections count of over 50. Actually, it keeps increasing up until 800 after which the database stops refusing connections (obviously).
Why is the connection pool maximum capacity not respected?
We're running WebLogic 10.3.5 and the connection pool is connected to an Oracle database using the oracle.jdbc.OracleDriver driver.
Yes, pinned-to-thread is documented to override your init-max settings because it must make
a connection per WebLogic execute-thread. If your application also spawns it's own threads
which get pool connections, you might have 800 threads (ugly), each with a connection.
It would indicate sub-optimal pool use too, which is best used by getting a connection, using it,
and closing it ASP, all within a single method call, so connections are not retained for long periods
by any thread.