[DERBY-3526] AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk

• 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: V.Narayanan
• Reporter: Jorgen Loland
• Created: 12/Mar/08 14:39
• Updated: 02/May/13 02:29
• Resolved: 07/Apr/08 08:47

Description

The replication log shipper thread synchronizes on 'this' both when shipping log records (shipALogChunk) and when it waits between log shipments.

Transaction threads may try to wake up the log shipper because log has arrived that should be shipped (i.e., through the method workToDo). These threads should not have to wait for the monitor if the log shipper is currently busy shipping log. The solution is to have two monitors - one for log shipment and one for waiting between log shipment.

This may seem like a minor issue, but if the TCP connection between master and slave is lost e.g. because a network cable has been unplugged, the log shipper will block for 2 minutes on ObjectOutputStream#writeObject.

Issue Links

• depends upon: DERBY-3539 Add possibility to inject errors in replication message layer