[
https://issues.apache.org/jira/browse/DERBY-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-3329.
------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed 'derby-3329-2b-enable_statement_pooling-cpds.diff' to trunk with
revision 632338.
Statement pooling is now enabled, and can be tested by obtaining connections
through a ClientConnectionPoolDataSource with 'maxStatements' set to somthing
larger than zero. The property follows the JavaBean standard, so you would use
cpDs.setMaxStatements(int) to specify a value.
Note that there are some known problems with the feature. I would like to get
feedback on all problems to check if it is an existing bug or something newly
introduced.
I'm away for one week and will pick up the work again (bug fixing) when I get
back.
> Enable statement pooling in the client JDBC driver
> --------------------------------------------------
>
> Key: DERBY-3329
> URL: https://issues.apache.org/jira/browse/DERBY-3329
> Project: Derby
> Issue Type: Sub-task
> Components: JDBC, Network Client
> Affects Versions: 10.4.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Fix For: 10.4.0.0
>
> Attachments: derby-3329-1a-enable_statement_pooling.diff,
> derby-3329-1b-enable_statement_pooling.diff,
> derby-3329-2a-enable_statement_pooling-cpds.diff,
> derby-3329-2b-enable_statement_pooling-cpds.diff,
> derby-3329-3a_stmtpooling_tests_NO_COMMIT.diff,
> derby-3329-3b_stmtpooling_tests.diff
>
>
> Enable statement pooling in the client JDBC driver.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
