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

["Jørgen Løland (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578657#action_12578657 ] 

Jørgen Løland commented on DERBY-3509:
--------------------------------------

The log shipper thread also has to be restarted when the network has been reestablished since the log shipper thread will terminate if the socket is shutdown.

> The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3509
>                 URL: https://issues.apache.org/jira/browse/DERBY-3509
>             Project: Derby
>          Issue Type: Bug
>          Components: Newcomer, Replication
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.