[DERBY-3924] Create test for restart of slave after master has crashed

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.4.2.1, 10.5.1.1
• Component/s: Replication, Test
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 27/Oct/08 13:36
• Updated: 30/Jun/09 23:37

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.

Issue Links

• relates to: DERBY-3878 Replication: stopSlave does not close serversocket when master has crashed.