Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14650 invoked from network); 29 Feb 2008 16:43:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Feb 2008 16:43:55 -0000 Received: (qmail 7255 invoked by uid 500); 29 Feb 2008 16:43:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 7195 invoked by uid 500); 29 Feb 2008 16:43:49 -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 7175 invoked by uid 99); 29 Feb 2008 16:43:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 08:43:49 -0800 X-ASF-Spam-Status: No, hits=-1998.8 required=10.0 tests=ALL_TRUSTED,FS_REPLICA 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 16:43:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A34BB234C059 for ; Fri, 29 Feb 2008 08:42:55 -0800 (PST) Message-ID: <1903648297.1204303375667.JavaMail.jira@brutus> Date: Fri, 29 Feb 2008 08:42:55 -0800 (PST) From: "V.Narayanan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3428) Doing a replication failover should shutdown the database and the connection should no longer be available In-Reply-To: <779649975.1203316954741.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-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573823#action_12573823 ] V.Narayanan commented on DERBY-3428: ------------------------------------ Thank you for the commit Oystein > Doing a replication failover should shutdown the database and the connection should no longer be available > ---------------------------------------------------------------------------------------------------------- > > Key: DERBY-3428 > URL: https://issues.apache.org/jira/browse/DERBY-3428 > Project: Derby > Issue Type: Bug > Components: Replication > Affects Versions: 10.4.0.0 > Reporter: V.Narayanan > Assignee: V.Narayanan > Attachments: Derby3428.diff, Derby3428.stat, Derby3428_v1.diff, Derby3428_v1.stat, Derby3428_v2.diff, Derby3428_v2.stat > > > Oystein says (as part of comments in Derby-3205) > After executing a failover, I am told that the database is shut down, but I still able to use the connection to access the database: > ij version 10.4 > ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass'; > ij> call syscs_util.syscs_freeze_database(); > 0 rows inserted/updated/deleted > ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass;startMaster=true;slaveHost=localhost'; > ij(CONNECTION1)> call syscs_util.syscs_unfreeze_database(); > 0 rows inserted/updated/deleted > ij(CONNECTION1)> connect 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true'; > ERROR XRE20: Failover performed successfully for database 'null', the database has been shutdown. > ij(CONNECTION1)> select * from t; > I > ----------- > 1 > 2 > 3 > 4 > 5 > 6 > 7 > 8 > 9 > 10 > 10 > 11 rows selected > ij(CONNECTION1)> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.