RE: Weblogic connection pools (JDBC)

  • From: "Borrill, Christopher" <Chris.Borrill@xxxxxx>
  • To: "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 15 Dec 2006 15:50:53 +1300

This blog entry, appears to indicate you are on the right track:

I do not think increasing this value will require significant extra
resources on the app server, but the database is a different matter, you
will probably have to increase MAX_OPEN_CURSORS.


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Norris
Sent: Friday, 15 December 2006 12:58 p.m.
Subject: Weblogic connection pools (JDBC)

Is there any sort of baseline recommendation for the StatementCacheSize
setting when using Weblogic connection pooling?
I'm involved in some load testing of a 3rd-party application, and the
only significant issue we're seeing is a parse-to-execute ratio of
(essentially) 1:1.  I've been told that we're using the default cache
size of 10 statements, which sounds woefully inadequate to me... I'm
tempted to ask for a substantial increase, such as to 50 or 100.
Unfortunately I'm not Weblogic-savvy, and so don't have any real
appreciation for the additional resources this would require on the
appserver.  I realize this is rather vague, but would appreciate any
suggestions that I might use as a starting point.

For what it's worth, I do intend to ask our vendor contact if they have
any recommendations on this matter.  It might take a few days to get an
answer, however, so I thought it would be worth checking into here as


"I'm too sexy for my code." - Awk Sed Fred.


Other related posts: