What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the initial settings in a production environment?

Question

Options

• AEnsure the maximum size is increased to an appropriate setting.
• BSet the minimum and maximum size of the connection pool to the same value.
• CIncrease the statement cache size.
• DAdd more heap to the JVM.
• EAdd more nodes to the cluster.

• A
  76% (34)
• D
  9% (4)
• E
  16% (7)

Explanation

Tuning a WebLogic JDBC connection pool starts with A: increasing the maximum pool size so the server can handle peak load without exhausting connections, then B: equalizing the min and max size to eliminate the overhead of dynamically creating/destroying connections at runtime (a pre-warmed pool reduces latency spikes), and finally C: increasing the statement cache size so frequently executed SQL statements are reused rather than re-parsed by the database.

D (adding JVM heap) addresses memory pressure, not connection pool behavior - it's a separate JVM-level tuning concern. E (adding cluster nodes) is a scaling strategy, not a pool tuning step; each node still needs its own properly tuned pool.

Memory tip: Think "Max → Match → Cache" - first raise the ceiling, then lock the floor to meet it, then cache statements for speed. These three steps move in order from capacity → stability → performance.

No community discussion yet for this question.