Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 70886 invoked from network); 7 Jul 2009 12:40:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Jul 2009 12:40:29 -0000 Received: (qmail 8834 invoked by uid 500); 7 Jul 2009 12:40:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 8810 invoked by uid 500); 7 Jul 2009 12:40:39 -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 8802 invoked by uid 99); 7 Jul 2009 12:40:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Jul 2009 12:40:39 +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; Tue, 07 Jul 2009 12:40:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2B722234C1F0 for ; Tue, 7 Jul 2009 05:40:15 -0700 (PDT) Message-ID: <1885910513.1246970415177.JavaMail.jira@brutus> Date: Tue, 7 Jul 2009 05:40:15 -0700 (PDT) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3417) slave side stop in a client server mode results in SQLState printed without proper error message In-Reply-To: <25294191.1202984349407.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-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728066#action_12728066 ] Dag H. Wanvik commented on DERBY-3417: -------------------------------------- Thanks for reminding me; I agree, I'll do it. > slave side stop in a client server mode results in SQLState printed without proper error message > ------------------------------------------------------------------------------------------------ > > Key: DERBY-3417 > URL: https://issues.apache.org/jira/browse/DERBY-3417 > Project: Derby > Issue Type: Bug > Components: Replication > Affects Versions: 10.4.1.3 > Reporter: V.Narayanan > Assignee: Dag H. Wanvik > Attachments: derby-3417-2.diff, derby-3417-2.stat, derby-3417.diff, derby-3417.stat > > > I tried a stopSlave on the slave side of the replication system and > found the below > ij> connect 'jdbc:derby://localhost:1528/replicationdb;stopSlave=true'; > ERROR XRE41: DERBY SQL error: SQLCODE: -1, SQLSTATE: XRE41, SQLERRMC: XRE41 > https://issues.apache.org/jira/browse/DERBY-3205 says > ERROR XRE41: Replication operation 'failover' or 'stopSlave' failed because the connection with the master is working. Issue the 'failover' or 'stopMaster' operation on the master database instead. > needs to be printed. > I am not sure if this is a generic case for client server replication messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.