Description of problem: Currently the qpid C++ libraries do not support running over IPv6 at all. Given the nearterm exhaustion of the IPv4 address space there will be increasing interest in running over IPv6, so we should make qpid work with IPv6.
The work to enable IPv6 connections has been done upstream and should be available for C++/Python implementations from qpid 0.14 The caveats to this: SSL currently doesn't work over IPv6, The state of the java client is unknown - it will probably make connections over IPv6, but the reconnect logic may not be correct and it will currently not parse IPv6 literal addresses. The windows c++ port should also work with IPv6.
C++ and C# clients on Windows support IPv6 addressing; tested on packages qpid-cpp-win-2.2.0.1-1. Python clients and qpid-tools on Windows do not support IPv6 addressing yet; see https://bugzilla.redhat.com/show_bug.cgi?id=788040
There are some issues, that we discovered with IPv6 functionality. Please check out Bug 790571 Bug 790570 Bug 790565 Bug 790562 Bug 790004 Bug 785195 and set/unset depends on as appropriate to pass this functionality.
https://bugzilla.redhat.com/show_bug.cgi?id=802466 See above for cluster related issues.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This release introduces TCP/IPv6 support to the broker and C++ client and python client libraries. There are the following known limitations to this support: SSL is not supported over TCPv6. Cluster connections that use literal IPv6 addresses will not work correctly.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,4 @@ -This release introduces TCP/IPv6 support to the broker and C++ client and python client libraries. +This release introduces TCP/IPv6 support to the broker and C++ and python client libraries. There are the following known limitations to this support:
Testing packages: python-qpid-0.14-3.el5 python-qpid-qmf-0.14-3.el5 qpid-cpp-client-0.14-10.el5 qpid-cpp-client-devel-0.14-10.el5 qpid-cpp-client-devel-docs-0.14-10.el5 qpid-cpp-client-ssl-0.14-10.el5 qpid-cpp-server-0.14-10.el5 qpid-cpp-server-cluster-0.14-10.el5 qpid-cpp-server-devel-0.14-10.el5 qpid-cpp-server-ssl-0.14-10.el5 qpid-cpp-server-store-0.14-10.el5 qpid-cpp-server-xml-0.14-10.el5 qpid-java-client-0.14-3.el5 qpid-java-common-0.14-3.el5 qpid-java-example-0.14-3.el5 qpid-qmf-0.14-3.el5 qpid-qmf-devel-0.14-3.el5 qpid-tools-0.14-1.el5 python-qpid-0.14-1.el6.noarch python-qpid-qmf-0.14-4.el6.x86_64 qpid-cpp-client-0.14-10.el6.x86_64 qpid-cpp-client-devel-0.14-10.el6.x86_64 qpid-cpp-client-devel-docs-0.14-10.el6.noarch qpid-cpp-client-ssl-0.14-10.el6.x86_64 qpid-cpp-server-0.14-10.el6.x86_64 qpid-cpp-server-cluster-0.14-10.el6.x86_64 qpid-cpp-server-devel-0.14-10.el6.x86_64 qpid-cpp-server-ssl-0.14-10.el6.x86_64 qpid-cpp-server-store-0.14-10.el6.x86_64 qpid-cpp-server-xml-0.14-10.el6.x86_64 qpid-java-client-0.14-3.el6.noarch qpid-java-common-0.14-3.el6.noarch qpid-java-example-0.14-3.el6.noarch qpid-qmf-0.14-4.el6.x86_64 qpid-qmf-debuginfo-0.12-6.el6.x86_64 qpid-tests-0.12-1.el6.noarch qpid-tools-0.12-2.el6.noarch ruby-qpid-0.7.946106-2.el6.x86_64 tested on RHEL 5.8, 6.2 & i386, x86_64 -> VERIFIED Note that there is still some existing issues (see comment #7)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0529.html