[DERBY-3509] The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3, 10.5.1.1
• Component/s: Replication
• Assignee: V.Narayanan
• Reporter: Jorgen Loland
• Created: 07/Mar/08 10:58
• Updated: 02/Jun/10 11:13
• Resolved: 04/Apr/08 09:06

Description

In MasterController#handleException, a new ReplicationMessageTransmit object is created if the exception is IOException. However, the logShipper is not notified that the new transmitter should be used. A possible solution would be to add a setTransmitter method to AsynchronousLogShipper. Note that the logShipper may contain state information that cannot be discarded, so it cannot be reinstantiated.