Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 64198 invoked from network); 2 Apr 2008 10:16:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Apr 2008 10:16:59 -0000 Received: (qmail 11218 invoked by uid 500); 2 Apr 2008 10:16:54 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 11184 invoked by uid 500); 2 Apr 2008 10:16:54 -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 11154 invoked by uid 99); 2 Apr 2008 10:16:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Apr 2008 03:16:54 -0700 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; Wed, 02 Apr 2008 10:16:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7E7F3234C0B7 for ; Wed, 2 Apr 2008 03:14:24 -0700 (PDT) Message-ID: <88739701.1207131264516.JavaMail.jira@brutus> Date: Wed, 2 Apr 2008 03:14:24 -0700 (PDT) From: =?utf-8?Q?=C3=98ystein_Gr=C3=B8vlen_=28JIRA=29?= To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-3549) Unable to start slave mode after authentication failure on a previous startSlave attempt In-Reply-To: <1929636736.1205679624372.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3549?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] =C3=98ystein Gr=C3=B8vlen resolved DERBY-3549. ------------------------------------ Resolution: Fixed Fix Version/s: 10.4.1.0 Merged to 10.4 branch at revision 643828. > Unable to start slave mode after authentication failure on a previous sta= rtSlave attempt > -------------------------------------------------------------------------= --------------- > > Key: DERBY-3549 > URL: https://issues.apache.org/jira/browse/DERBY-3549 > Project: Derby > Issue Type: Bug > Components: Replication > Affects Versions: 10.4.0.0, 10.5.0.0 > Reporter: V.Narayanan > Assignee: J=C3=B8rgen L=C3=B8land > Fix For: 10.4.1.0, 10.5.0.0 > > Attachments: derby-3549-1a.diff, derby-3549-1a.stat, derby-3549-1= b.diff, derby-3549-1b.stat > > > Trying a startSlave after an initial startSlave fails due to an authentic= ation failure throws an error > saying that the database has already been booted > vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derb= y.tools.ij > ij version 10.5 > ij> connect 'jdbc:derby:mydb;startSlave=3Dtrue;slaveHost=3Dlocalhost;slav= ePort=3D8001'; > ERROR 08004: Connection authentication failure occurred. Reason: Invalid= authentication.. > ij> connect 'jdbc:derby:mydb;startSlave=3Dtrue;user=3Doystein;password=3D= pass;slaveHost=3Dlocalhost;slavePort=3D8001'; > ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The= database has already been booted.=20 > ij> --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.