Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 74906 invoked from network); 10 Aug 2009 15:58:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Aug 2009 15:58:34 -0000 Received: (qmail 59265 invoked by uid 500); 10 Aug 2009 15:58:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 59245 invoked by uid 500); 10 Aug 2009 15:58:41 -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 59227 invoked by uid 99); 10 Aug 2009 15:58:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 15:58:41 +0000 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; Mon, 10 Aug 2009 15:58:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1A368234C1ED for ; Mon, 10 Aug 2009 08:58:17 -0700 (PDT) Message-ID: <697725819.1249919897106.JavaMail.jira@brutus> Date: Mon, 10 Aug 2009 08:58:17 -0700 (PDT) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4345) Inconsistent behavior regarding shutting down embedded engine from ClientDataSource and ClientDriver/DriverManager In-Reply-To: <1151930147.1249677194881.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741392#action_12741392 ] Dag H. Wanvik commented on DERBY-4345: -------------------------------------- I tried to change your repro to use DriverManager, but for me it seems to behave the same as ClientDataSource? I may be doing something wrong; it would be nice to add that to the repro to show that it does not shut down the engine. > Inconsistent behavior regarding shutting down embedded engine from ClientDataSource and ClientDriver/DriverManager > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-4345 > URL: https://issues.apache.org/jira/browse/DERBY-4345 > Project: Derby > Issue Type: Bug > Components: Network Server > Affects Versions: 10.5.1.1 > Environment: Windows Vista with JDK 1.6 > Reporter: Lily Wei > Priority: Minor > Attachments: ReproDerby3532.java > > > When investigate DERBY-3532, Kathey and I found inconsistent behavior in turn of connection modes possible to shut down the engine underneath the network server. Currently, users can shutdown from the client remotely with ClientDataSource but not with ClientDriver/DriverManager. The two should be the same. > Should we disable the capability for ClientDataSource or enable it for ClientDriver? I am leaning toward to disable the capability for ClientDataSource. However, I am not sure about the risk of functionality disable impact for existing production customers. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.