db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3509) The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.
Date Tue, 01 Apr 2008 10:46:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

V.Narayanan updated DERBY-3509:
-------------------------------

    Attachment: Derby3509_1.stat
                Derby3509_1.diff

I have modified the handleException method to return the transmitter
object that is created.

The log shipper bases its decision on whether it should continue with the
log shipping based on if a valid transmitter object is created.

> 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
>         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.


Mime
View raw message