[
https://issues.apache.org/jira/browse/ZOOKEEPER-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083338#comment-14083338
]
Hongchao Deng commented on ZOOKEEPER-2000:
------------------------------------------
{code}
public void process(WatchedEvent event) {}});
for (int i = 0; i < 10; i++) {
try {
Thread.sleep(1000);
zkArr[followerIndex].setData("/test", "teststr".getBytes(), -1);
Assert.fail("New client connected to old client port!");
} catch (KeeperException.ConnectionLossException e) {
}
{code}
code format.
> Fix ReconfigTest.testPortChange
> -------------------------------
>
> Key: ZOOKEEPER-2000
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2000
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Priority: Minor
> Fix For: 3.5.1
>
> Attachments: ZOOKEEPER-2000.patch
>
>
> testPortChange changes all ports and role of the server and thus causes
> existing clients to disconnect, while this wouldn't happen if only the client
> port changes. Need to fix it to only change client port and not all the other
> parameters and make sure that the clients don't disconnect, while new clients
> shouldn't be able to connect to the old port.
--
This message was sent by Atlassian JIRA
(v6.2#6252)