[jira] Resolved: (DERBY-3527) The slave will not notice that a network cable is unplugged and will therefore reject failover/stopSlave commands

["Øystein Grøvlen (JIRA)" <ji...@apache.org>]

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

Øystein Grøvlen resolved DERBY-3527.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.5.0.0

Fix merged to 10.4 branch at revision 643861.

> The slave will not notice that a network cable is unplugged and will therefore reject failover/stopSlave commands
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3527
>                 URL: https://issues.apache.org/jira/browse/DERBY-3527
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication
>    Affects Versions: 10.4.0.0, 10.5.0.0
>            Reporter: Jørgen Løland
>            Assignee: Jørgen Løland
>             Fix For: 10.4.1.0, 10.5.0.0
>
>         Attachments: derby-3527-1a.diff, derby-3527-1a.stat, derby-3527-1b.diff, derby-3527-1b.stat, derby-3527-1c.diff, derby-3527-1c.stat, derby-3527-1d.diff
>
>
> If a network cable between the master and slave is unplugged (or a switch crashes etc), ObjectInputStream#readObject will not get an exception. Neither the socket nor the input stream can be queried for information on whether or not the connection is working. AFAIK, the only way to find out if the network is down is to send a message.
> The slave commands stopSlave and failover are rejected if the network connection is working. To be absolutely sure that the connection is working, we need to ping the master when these commands are requested.

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