[DERBY-3567] AsynchronousLogShipper#forceFlush should time out

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: Replication
• Assignee: Jorgen Loland
• Reporter: Jorgen Loland
• Created: 25/Mar/08 09:16
• Updated: 02/Jun/10 11:12
• Resolved: 04/Apr/08 14:59

Description

If the network connection to the slave is lost, ObjectOutputStream#writeObject may be blocked for 2 minutes before failing (not configurable TCP property).

Currently, ALS#forceFlush sends a chunk of log to the slave using the client thread. The client thread cannot be blocked for 2 minutes before giving up. Rather, it should notify the log shipper that it has to send log immediately, and then wait for a short while (until notified or e.g. maximum 5 seconds). If the log shipper has not been able to empty some space in the log buffer by then, replication should be stopped.