Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

Thank you Chris. -Jaikiran On 01/04/20 6:40 pm, Chris Hegarty wrote: > > >> On 1 Apr 2020, at 13:48, Jaikiran Pai > > wrote: > ... Now that you explained it to me, I see what you mean and what that javadoc means. I hadn't paid attention to the "

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

> On 1 Apr 2020, at 13:48, Jaikiran Pai wrote: ... >>> Now that you explained it to me, I see what you mean and what that javadoc >>> means. I hadn't paid attention to the "This String is constructed by >>> calling toString() on the InetAddress and concatenating the port number >>> (with

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

On 01/04/20 3:49 pm, Julia Boes wrote: > > Hi Jaikiran, > By the way, keeping aside the breaking nature of this change, the current javadoc, I think doesn't reflect what the current implementation returns for unresolved addresses. The javadoc states: "If the address is unr

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

Hi Jaikiran, By the way, keeping aside the breaking nature of this change, the current javadoc, I think doesn't reflect what the current implementation returns for unresolved addresses. The javadoc states: "If the address is unresolved, || is displayed in place of the address literal." Not

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

Hello Chris, On 30/03/20 1:49 pm, Chris Hegarty wrote: > Hi Jaikiran, > > Thank you for posting this message to net-dev. > > TL;DR seems like the specific issue raised against Quarkus has been > resolved ( by upgrading to a more recent version of ZooKeeper ). That's correct. > >> So this looks l

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

Hello Alan, On 30/03/20 1:31 pm, Alan Bateman wrote: > On 28/03/2020 06:43, Jaikiran Pai wrote: >> >> There's an issue raised in Quarkus repo[1], where Apache Kafka >> (embedded) no longer starts on Java 14. From what I can see the root >> cause is this[2]. >> >> JDK-8225499[3] changed the impleme

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

Hi Jaikiran, Thank you for posting this message to net-dev. TL;DR seems like the specific issue raised against Quarkus has been resolved ( by upgrading to a more recent version of ZooKeeper ). > On 28 Mar 2020, at 06:43, Jaikiran Pai wrote: > > There's an issue raised in Quarkus repo[1], whe

Re: Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

On 28/03/2020 06:43, Jaikiran Pai wrote: There's an issue raised in Quarkus repo[1], where Apache Kafka (embedded) no longer starts on Java 14. From what I can see the root cause is this[2]. JDK-8225499[3] changed the implementation (and even the javadoc) of the InetSocketAddress.toString()

Java 14 - Change in InetSocketAddress.toString() behaviour seems to be causing issues

There's an issue raised in Quarkus repo[1], where Apache Kafka (embedded) no longer starts on Java 14. From what I can see the root cause is this[2]. JDK-8225499[3] changed the implementation (and even the javadoc) of the InetSocketAddress.toString() which now reads[4]: "... If the address is un