Production server JDBC configuration

Question

Anybody knows what is the way to configure the JDBC pooling parameters such as init & max capacity
for production server? Any references for this?
Thanks

Answer 1

Shiye Qiu wrote:
Joe,
We use WLS 8.1SP4, Oracle 10g, no firewall at all.
I could recall that I saw some guidelines from BEA
somewhere sometime ago but I could not find it
Thanks
QiuAnd how is the pool used? Generated EJBs or hand-written JDBC?
Will every user of WebLogic need pool access?
Typically a user will want one pool connection per invoke,
and typically the connection is reserved, used, and returned
to the pool during each server-invoke from a user. However, no
matter how many concurrent users there may be, the server only
has a set number of threads that will handle user calls, so
the pool ideally needs only N connections for an N-thread server.
If you have a refresh time set for the pool (so it asynchronously
tests idle connections) add 1.
I would have the pool make all the connections at startup,
so I would recommend initial capacity = max capacity = (N + 1).
I would have test-on-reserve true, and no other testing. I
would set the statement cache to hold all the prepared statements
the application would use, and for Oracle I would make sure the
DBMS is configured to allow a connection to have as many cursors
as the statement cache would require, at least. If performance
was tested and found to be necessarily better with test-on-reserve
false, I would consider using the new secondsToTrustAnIdlePoolConnection
to allow test-on-reserve to go back to true, but skip some testing
with recently used connections. Thsi depends on how tolerant the application
might be to occasionally getting a bad connection and how reliable the
DBMS is etc.
Joe
Joe