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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/10/27 14:38:44 UTC

[jira] Created: (DERBY-3924) Create test for restart of slave after master has crashed

Create test for restart of slave after master has crashed
---------------------------------------------------------

                 Key: DERBY-3924
                 URL: https://issues.apache.org/jira/browse/DERBY-3924
             Project: Derby
          Issue Type: Test
          Components: Replication, Test
    Affects Versions: 10.4.2.1, 10.5.0.0
            Reporter: Knut Anders Hatlen
            Priority: Minor


The fix for DERBY-3878 didn't include a regression test. We should add a new test case to the replication tests that does the following:

1) start slave
2) start master
3) kill master without stopping it first
4) stop slave, but leave the slave JVM running
5) start a new slave using the same port as the slave stopped in (4)

Step (5) should cause an address-already-in-use exception without the fix for DERBY-3878.

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

[jira] Updated: (DERBY-3924) Create test for restart of slave after master has crashed

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

    Issue Type: Improvement  (was: Test)

> Create test for restart of slave after master has crashed
> ---------------------------------------------------------
>
>                 Key: DERBY-3924
>                 URL: https://issues.apache.org/jira/browse/DERBY-3924
>             Project: Derby
>          Issue Type: Improvement
>          Components: Replication, Test
>    Affects Versions: 10.4.2.1, 10.5.1.1
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>
> The fix for DERBY-3878 didn't include a regression test. We should add a new test case to the replication tests that does the following:
> 1) start slave
> 2) start master
> 3) kill master without stopping it first
> 4) stop slave, but leave the slave JVM running
> 5) start a new slave using the same port as the slave stopped in (4)
> Step (5) should cause an address-already-in-use exception without the fix for DERBY-3878.

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