Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2125902434.1212947625039.JavaMail.jira@brutus>
Date: Sun, 8 Jun 2008 10:53:45 -0700 (PDT)
From: "V.Narayanan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Issue Comment Edited: (DERBY-3632) Replication tests must
 ensure stable replication state has been reached before attempting further
 connection or new replication commands.
In-Reply-To: <229334152.1208514505134.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603415#action_12603415 ] 

narayanan edited comment on DERBY-3632 at 6/8/08 10:53 AM:
-------------------------------------------------------------

The patch for the issue seems straightforward to me, will commit this patch
if my tests pass. Starting test runs now.

      was (Author: narayanan):
    The issue seems straightforward to me, will commit this issue
if my tests pass. Starting test runs now.
  
> 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
>         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.