db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3549) Unable to start slave mode after authentication failure on a previous startSlave attempt
Date Sun, 16 Mar 2008 15:00:24 GMT
Unable to start slave mode after authentication failure on a previous startSlave 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


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>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message