Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 59330 invoked from network); 7 Aug 2009 20:33:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Aug 2009 20:33:30 -0000 Received: (qmail 52994 invoked by uid 500); 7 Aug 2009 20:33:37 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 52917 invoked by uid 500); 7 Aug 2009 20:33:37 -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 52908 invoked by uid 99); 7 Aug 2009 20:33:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Aug 2009 20:33:37 +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; Fri, 07 Aug 2009 20:33:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D75F829A0016 for ; Fri, 7 Aug 2009 13:33:14 -0700 (PDT) Message-ID: <1151930147.1249677194881.JavaMail.jira@brutus> Date: Fri, 7 Aug 2009 13:33:14 -0700 (PDT) From: "Lily Wei (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-4345) Inconsistent behavior regarding shutting down embedded engine from ClientDataSource and ClientDriver/DriverManager 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 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 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.