[DERBY-3878] Replication: stopSlave does not close serversocket when master has crashed.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.2.0
• Fix Version/s: 10.4.2.1, 10.5.1.1
• Component/s: Replication
• Issue & fix info: Newcomer
• Assignee: Knut Anders Hatlen
• Reporter: Jorgen Loland
• Created: 16/Sep/08 11:51
• Updated: 02/Jun/10 11:12
• Resolved: 27/Oct/08 13:39

Description

The stopSlave command (connection URL attribute) fails to close the ServerSocket when called after master database has crashed. Because of this, the same Derby instance cannot later start a slave on the same port.

The problem is in ReplicationMessageReceive#tearDown and SocketConnection#tearDown:

SC#tearDown:
When objOutputStream is closed, the stream's flush method is called. Flush throws an exception, and socket.close is not called.

RMR#tearDown:
When socketCon.teardown throws an exception, serverSocket.close is not called.

Suggested fix: add try/catch/finally blocks so that vital code (socket.close and serverSocket.close) is always called.

Note that the stop slave command can also come from the master (if stopMaster connection URL is called), in which case this bug will not materialize.

Issue Links

• is related to: DERBY-3924 Create test for restart of slave after master has crashed