[
https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582273#action_12582273
]
Øystein Grøvlen commented on DERBY-3549:
----------------------------------------
I am also not quite sure what is the best error to get in the case
that you try start a slave on a already booted database with invalid
credentials. Should a a user that is not authorized to boot the
database, be able to learn whether it is booted or not through a
startSlave command?
> 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
> Assignee: Jørgen Løland
> Attachments: derby-3549-1a.diff, derby-3549-1a.stat
>
>
> Trying a startSlave after an initial startSlave fails due to an
> authentication failure throws an error
> saying that the database has already been booted
> [EMAIL PROTECTED]:~/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.
