[
https://issues.apache.org/jira/browse/BOOKKEEPER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160104#comment-13160104
]
Hudson commented on BOOKKEEPER-66:
----------------------------------
Integrated in bookkeeper-trunk #259 (See
[https://builds.apache.org/job/bookkeeper-trunk/259/])
BOOKKEEPER-66: use IPv4 for builds (mmorel via ivank)
ivank :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
* /zookeeper/bookkeeper/trunk/bookkeeper-server/bin/bookkeeper
* /zookeeper/bookkeeper/trunk/hedwig-server/bin/hedwig
* /zookeeper/bookkeeper/trunk/pom.xml
> use IPv4 for builds
> -------------------
>
> Key: BOOKKEEPER-66
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-66
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Matthieu Morel
> Assignee: Matthieu Morel
> Fix For: 4.0.0
>
> Attachments: BOOKKEEPER-66.patch, BOOKKEEPER-66.patch
>
>
> On some linux boxes that run a dual IPv6-IPv4 network stack, with IPv6
> enabled (e.g. debian-based), there is an issue with some java programs,
> preventing network connections.
> This results in
> "org.apache.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ledgers" in BookieZKExpireTest test
> (for instance) but is actually due to a previous
> "java.net.NoRouteToHostException: Network is
> unreachable" issue.
> I could reproduce this on a debian 6 for instance, and the issue is similar
> another one detailed in a Hadoop ticket:
> https://issues.apache.org/jira/browse/HADOOP-6056
> We should make sure IPv4 is used for builds so that one can build bookkeeper
> out of the box, without configuration changes to the OS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
