| Key: |
DBCP-164
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Dirk Verbeeck
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
|
|
Environment:
|
Operating System: All
Platform: All
Operating System: All
Platform: All
|
|
|
Patch posted on commons-dev 29-02-2004 by Todd Carmichael
==========================================================
Currently there is not much configurability for the prepared statement
pooling. This patch defines a new property on the driveradaptercpds class:
maxPreparedStatements. If this value is set to something other than -1,
then the underlying statement pool will not use an evictor thread and will
use the maxTotal mechanism to remove the oldest objects. If set to -1,
then the old behavior is used. You may find this patch useful. In our
environment we are concerned about creating a separate thread for EVERY
connection.
|
|
Description
|
Patch posted on commons-dev 29-02-2004 by Todd Carmichael
==========================================================
Currently there is not much configurability for the prepared statement
pooling. This patch defines a new property on the driveradaptercpds class:
maxPreparedStatements. If this value is set to something other than -1,
then the underlying statement pool will not use an evictor thread and will
use the maxTotal mechanism to remove the oldest objects. If set to -1,
then the old behavior is used. You may find this patch useful. In our
environment we are concerned about creating a separate thread for EVERY
connection. |
Show » |
|
enhancements to prepared statement in DriverAdapterCPDS
patch_dbcp_maxpreparedStatements