db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3383) Replication: stopSlave boots database?
Date Mon, 11 Feb 2008 09:40:08 GMT

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

Øystein Grøvlen updated DERBY-3383:

Turns out it was ij which confused me.  Entering something that ij is not able to parse before
a connection has been establish, will not tell you about the parse error.  (For some reason
emacs-shell interpreted 'ij>' as part of the command.

Committed patch as revision  620444.

> 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