This was with Java 6, Java has postponed the fix for NIO to Java 7. But I could have easily read that wrong.
Is this with Java 5 ?
On Tue, Feb 1, 2011 at 11:08 PM, Hammond, Steven <Steven.Hammond@polycom.com> wrote:
I may have spoken too soon. I thought we had this resolved, but our QA person just came by and said IPV6 searches are not working if the DNS record for our ApacheDS server does not have an IPv4 record in addition to the IV6 record.
We tried to work around by putting in the ipv6 listner in LDAPserver code, but we run into this stack trace. Again, this is on 1.5.3.
I set up the LdapServer on my dev box so that it would "try" to listen using an IPV6 address:
2011-01-25 13:14:36,508;3219;ERROR;ds.PlcmLdapServer;(main);(null_0) Failed to bind an LDAP service (/dead:0:0:0:20c:29ff:fef3:b3fc:389) to the service registry.
java.net.SocketException: Address family not supported by protocol family: bind
at sun.nio.ch.Net.bind(Native Method)
2011-01-25 13:14:36,508;3219;ERROR;ds.DsServiceImpl;(main);(null_0) failed to start apacheds
The interesting part is what I found when I googled the error:
From: Felix Knecht [mailto:email@example.com]
Sent: Tuesday, February 01, 2011 1:08 AM
To: Apache Directory Developers List
As we all know, IPv4 will run out in the next weeks/months/year ...
Is ApacheDS already IPv6 ready?
Do we need to keep this in mind when doing the refactoring now?
At least I saw hardcoded localhost (127.0.0.1) IP addresses in the code...
Sure it's nod a need for the next release, but after?