db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3392) Performing failover on a database not being replicated should give a more meaningful error message.
Date Mon, 11 Feb 2008 05:44:07 GMT

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

V.Narayanan updated DERBY-3392:
-------------------------------

    Derby Info: [Patch Available]

> Performing failover on a database not being replicated should give a more meaningful
error message.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3392
>                 URL: https://issues.apache.org/jira/browse/DERBY-3392
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: Derby_3392_v1.diff, Derby_3392_v1.stat
>
>
> Oystein says
> "If I do failover on a database where replication has not been started, I get the following:
> ij version 10.4
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass';
> ij> connect 'jdbc:derby:masterDB;user=oystein;password=pass;failover=true';
> ERROR XRE21: Error occurred while performing failover for database 'masterDB', Failover
attempt was aborted.
> I think I should rather get an error that says that database is not being replicated.
(I get that if I try to stop replication on a non-replicated database)."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message