Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 70479 invoked from network); 29 Feb 2008 15:07:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Feb 2008 15:07:54 -0000 Received: (qmail 16650 invoked by uid 500); 29 Feb 2008 15:07:48 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16587 invoked by uid 500); 29 Feb 2008 15:07:48 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 16253 invoked by uid 99); 29 Feb 2008 15:07:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 07:07:47 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 15:07:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1E6C5234C04E for ; Fri, 29 Feb 2008 07:06:51 -0800 (PST) Message-ID: <557409656.1204297611123.JavaMail.jira@brutus> Date: Fri, 29 Feb 2008 07:06:51 -0800 (PST) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-3329) Enable statement pooling in the client JDBC driver In-Reply-To: <14836567.1200590614133.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.