[
https://issues.apache.org/jira/browse/DERBY-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jørgen Løland updated DERBY-3549:
---------------------------------
Attachment: derby-3549-1b.stat
derby-3549-1b.diff
Thanks for reviewing the patch. Patch 1b addresses the issue that unauthorized
users should not get to know if a database has been booted or not.
All tests passed. Requesting review.
> 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,
> derby-3549-1b.diff, derby-3549-1b.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.
