[DERBY-3549] Unable to start slave mode after authentication failure on a previous startSlave attempt

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: Replication
• Assignee: Jorgen Loland
• Reporter: V.Narayanan
• Created: 16/Mar/08 14:59
• Updated: 21/Jan/11 17:51
• Resolved: 02/Apr/08 10:13

Description

Trying a startSlave after an initial startSlave fails due to an authentication failure throws an error
saying that the database has already been booted

vn@vn-laptop:~/work/workspaces/freshworkspace/slave$ java org.apache.derby.tools.ij
ij version 10.5
ij> connect 'jdbc:derby:mydb;startSlave=true;slaveHost=localhost;slavePort=8001';
ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
ij> connect 'jdbc:derby:mydb;startSlave=true;user=oystein;password=pass;slaveHost=localhost;slavePort=8001';
ERROR XRE09: Cannot start replication slave mode for database 'mydb'. The database has already been booted.
ij>