Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <343875585.1205495484376.JavaMail.jira@brutus>
Date: Fri, 14 Mar 2008 04:51:24 -0700 (PDT)
From: =?utf-8?Q?J=C3=B8rgen_L=C3=B8land_=28JIRA=29?= <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3539) Add possibility to inject errors in
 replication message layer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Add possibility to inject errors in replication message layer
-------------------------------------------------------------

                 Key: DERBY-3539
                 URL: https://issues.apache.org/jira/browse/DERBY-3539
             Project: Derby
          Issue Type: Improvement
          Components: Replication
    Affects Versions: 10.5.0.0
            Reporter: J=C3=B8rgen L=C3=B8land
            Priority: Minor


Some replication functionality is difficult to test automatically, e.g. bec=
ause human intervention is required. Examples of things that are difficult =
to test:

* behavior when the replication log buffer is nearly full
* network connection is lost without resulting in an exception (e.g., a net=
work cable is unplugged, a switch dies etc)

These scenarios would be easier to test automatically if we could inject er=
rors like randomly loosing log chunks, don't answer ping calls, not send lo=
g chunks for 1 minute etc.

Replication issues that need failure injection should link to this issue.

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