You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Øystein Grøvlen (JIRA)" <ji...@apache.org> on 2008/04/04 11:07:24 UTC
[jira] Resolved: (DERBY-3509) The replication log shipper is not
notified when a new replication transmitter is instantiated in
MC#handleException.
[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Øystein Grøvlen resolved DERBY-3509.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.4.1.0
Patch merged to 10.4 branch at revision 644646.
> 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
> Assignee: V.Narayanan
> Priority: Minor
> Fix For: 10.4.1.0, 10.5.0.0
>
> Attachments: Derby3509_1.diff, Derby3509_1.stat
>
>
> 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.