Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-3924

Create test for restart of slave after master has crashed

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.4.2.1, 10.5.1.1
    • Fix Version/s: None
    • Component/s: Replication, Test
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                knutanders Knut Anders Hatlen
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: