[
https://issues.apache.org/jira/browse/ZOOKEEPER-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892326#comment-13892326
]
Hadoop QA commented on ZOOKEEPER-1848:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12627041/zookeeper-1848_v1.patch
against trunk revision 1561672.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1919//console
This message is automatically generated.
> [WINDOWS] Java NIO socket channels does not work with Windows ipv6 on JDK6
> --------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1848
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1848
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Enis Soztutar
> Fix For: 3.5.0
>
> Attachments: zookeeper-1848_v1.patch
>
>
> ZK uses Java NIO to create ServerSorcket's from ServerSocketChannels. Under
> windows, the ipv4 and ipv6 is implemented independently, and Java seems that
> it cannot reuse the same socket channel for both ipv4 and ipv6 sockets. We
> are getting "java.net.SocketException: Address family not supported by
> protocol
> family" exceptions. When, ZK client resolves "localhost", it gets both v4
> 127.0.0.1 and v6 ::1 address, but the socket channel cannot bind to both v4
> and v6.
> The problem is reported as:
> http://bugs.sun.com/view_bug.do?bug_id=6230761
> http://stackoverflow.com/questions/1357091/binding-an-ipv6-server-socket-on-windows
> Although the JDK bug is reported as resolved, I have tested with jdk1.6.0_33
> without any success. Although JDK7 seems to have fixed this problem.
> See HBASE-6825 for reference.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
