[
https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-3632.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.6.1.0
I am marking this issue as Fixed in 10.6. It seems from looking over the linked
issues that most of these received fixes by that date.
Also changes were applied for this issue in 2009.
Very occassionally replication tests still fail - there are (or should be)
separate issues for that.
> 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, 10.6.1.0
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
