[
https://issues.apache.org/jira/browse/ZOOKEEPER-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927158#comment-16927158
]
Hudson commented on ZOOKEEPER-3540:
-----------------------------------
SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #689 (See
[https://builds.apache.org/job/ZooKeeper-trunk/689/])
ZOOKEEPER-3540: Avoid client port unavailable by skip binding the same
(eolivelli: rev 8460f4ed48c5f9018d882bee2be748de42e965f9)
* (add)
zookeeper-server/src/test/java/org/apache/zookeeper/server/NettyServerCnxnFactoryTest.java
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/NettyServerCnxnFactory.java
> Client port unavailable after binding the same client port during reconfig
> --------------------------------------------------------------------------
>
> Key: ZOOKEEPER-3540
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3540
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.0
> Reporter: Fangmin Lv
> Assignee: Fangmin Lv
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When dynamically replace a server with IPv4/IPv6 with the same port, the
> server will complain about 'address already in use', and cause the client
> port not available anymore.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
