Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 36898 invoked from network); 10 Aug 2009 22: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 22:58:34 -0000 Received: (qmail 22999 invoked by uid 500); 10 Aug 2009 22:58:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 22953 invoked by uid 500); 10 Aug 2009 22:58:40 -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 22936 invoked by uid 99); 10 Aug 2009 22:58:40 -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 22:58:40 +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 22:58:37 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BD9B0234C004 for ; Mon, 10 Aug 2009 15:58:16 -0700 (PDT) Message-ID: <1096698904.1249945096764.JavaMail.jira@brutus> Date: Mon, 10 Aug 2009 15:58:16 -0700 (PDT) From: "Lily Wei (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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:all-tabpanel ] Lily Wei updated DERBY-4345: ---------------------------- Attachment: ReproDerby4345.java Thanks Dag for looking at this. I attach the repro for DriverManager that can not shutdown the engine. I just this behavior should be consistent with EmbeddedDataSource. > 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, ReproDerby4345.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.