Hello everyone,
I would like to bring up the enhancement JDK-8257080[1] on this mailing
list.
tl;dr symptoms:
Java will use the first IP address from DNS and will fail to connect when
the target host is offline, even when the other IPs would have worked. This
is also true for the more recent Sock
On 16.12.20 13:49, Alan Bateman wrote:
On 16/12/2020 09:04, Benjamin Marwell wrote:
Hi Alan,
> I can't tell if your proposal is focused on the Socket constructors
> that take a hostname or more generally changing all APIs that
> connect to a SocketAddress to support co
On 16.12.20 16:12, Alan Bateman wrote:
On 16/12/2020 13:40, Benjamin Marwell wrote:
Huh… the APIs have already been changed which is why the issues above
exist. There is no workaround anymore.
Can you expand on this as it's not clear what you mean by "the APIs have
already cha
;
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> --
> *Von:* net-dev im Auftrag von Aleks
> Efimov
> *Gesendet:* Wednesday, December 16, 2020 5:53:02 PM
> *An:* Benjamin Marwell
> *Cc:* Alan Bateman ; OpenJDK Network Dev list <
> net-dev@openjdk.java.net>
> unless there are any objections, I will close 8257080
No objection from me.
> Things have moved on a lot since then, for example I see no reason why
> the Java HTTP Client, that uses non-blocking NIO socket channels, could
> not do it's own multi-connect thing.
Well, I am stuck with Java 8 and
resolution algo, which is just getAddresses()[0].
Am Sa., 26. Dez. 2020 um 15:53 Uhr schrieb Florian Weimer :
> * Benjamin Marwell:
>
> > Well, I am stuck with Java 8 and if any LDAP server goes down, all
> > java applications will, too. Python, .NET, etc. are not affecte
/JndiLdapContextFactory.java#L507-L509
Am Di., 29. Dez. 2020 um 07:39 Uhr schrieb Alan Bateman <
alan.bate...@oracle.com>:
> On 27/12/2020 10:05, Benjamin Marwell wrote:
> > Is there more than just one? The built-in will provide support
> > for javax.naming.spi.LdapDnsProvider from java
