You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jørgen Løland (JIRA)" <ji...@apache.org> on 2008/02/08 09:45:08 UTC
[jira] Reopened: (DERBY-3383) Replication: stopSlave boots
database?
[ https://issues.apache.org/jira/browse/DERBY-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jørgen Løland reopened DERBY-3383:
----------------------------------
A little too eager with this one - better leave the issue open until the patch has been committed ;)
> Replication: stopSlave boots database?
> --------------------------------------
>
> Key: DERBY-3383
> URL: https://issues.apache.org/jira/browse/DERBY-3383
> Project: Derby
> Issue Type: Bug
> Components: Replication
> Affects Versions: 10.4.0.0
> Reporter: Øystein Grøvlen
> Assignee: Jørgen Løland
> Attachments: derby-3383-1a.diff, derby-3383-1a.stat
>
>
> Looks like stopSlave on a not booted database leaves some traces:
> ij version 10.4
> ij> connect 'jdbc:derby:slaveDB;user=oystein;password=pass;stopSlave=true';
> ERROR XRE40: Could not perform operation because the database is not in replication slave mode.
> ij> connect 'jdbc:derby:slaveDB;user=oystein;password=pass;startSlave=true';
> ERROR XRE09: Cannot start replication slave mode for database 'slaveDB'. The database has already been booted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.