db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.
Date Thu, 14 May 2009 23:58:45 GMT

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

Dag H. Wanvik updated DERBY-3632:
---------------------------------

    Issue Type: Task  (was: Bug)

I make this issue a task since it is now a meta-issue, c.f the links to individual issues
of instabilities.

> 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: Task
>          Components: Replication, Test
>    Affects Versions: 10.4.2.0, 10.5.1.1
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>             Fix For: 10.4.2.1
>
>         Attachments: derby-3632_p1.diff.txt, derby-3632_p1.stat.txt
>
>
> 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.


Mime
View raw message