db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Løland (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3383) Replication: stopSlave boots database?
Date Tue, 05 Feb 2008 10:48:10 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jørgen Løland updated DERBY-3383:

    Attachment: derby-3383-1a.diff

Patch v1a fixes the reported problem. All tests passed - the patch is ready for review.

I will add a regression test for this once the replication test suite has been committed.
See DERBY-3161.

> 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:
>            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
> 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.

View raw message