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 "Ole Solberg (JIRA)" <ji...@apache.org> on 2008/04/18 14:56:21 UTC

[jira] Updated: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

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

Ole Solberg updated DERBY-3632:
-------------------------------

    Summary: Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.  (was: Replication tests must ensure stable replication state has been reached before attempting further connection or new replication replication commands.)

> Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3632
>                 URL: https://issues.apache.org/jira/browse/DERBY-3632
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication, Test
>    Affects Versions: 10.4.1.4, 10.5.0.0
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>
> When executing replication commands (startslave, startmaster, stopmaster, stopslave, failover) tests must make sure that correct replication state has been reached before attempting further connection to the master and slave databases.
> This causes intermittent errors in replication tests.

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