Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-03 Thread Rory O'Donnell
That is great news Mark. Thanks again for all your efforts ! Rgds,Rory On 03/08/2018 12:24, Mark Thomas wrote: On 03/08/18 11:11, Mark Thomas wrote: On 03/08/18 09:13, Rory O'Donnell wrote: Hi Mark, Did you include the latest patch - by the way this is being discussed on security-dev mailin

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-03 Thread Mark Thomas
On 03/08/18 11:11, Mark Thomas wrote: > On 03/08/18 09:13, Rory O'Donnell wrote: >> Hi Mark, >> >> Did you include the latest patch - by the way this is being discussed on >> security-dev mailing list ? > > Ah. No. I was using webrev.00 which was the one listed in the bug report > for JDK-8207009.

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-03 Thread Mark Thomas
On 03/08/18 09:13, Rory O'Donnell wrote: > Hi Mark, > > Did you include the latest patch - by the way this is being discussed on > security-dev mailing list ? Ah. No. I was using webrev.00 which was the one listed in the bug report for JDK-8207009. I'll try again with webrev.01 and report back.

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-03 Thread Rory O'Donnell
Hi Mark, Did you include the latest patch - by the way this is being discussed on security-dev mailing list ? see http://mail.openjdk.java.net/pipermail/security-dev/2018-August/017751.html Rgds,Rory On 02/08/2018 14:39, Mark Thomas wrote: On 02/08/18 13:42, Rory O'Donnell wrote: That w

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-02 Thread Mark Thomas
On 02/08/18 13:42, Rory O'Donnell wrote: > That would be very useful, thanks. Rory, I have testing this locally and the proposed patch for JDK-8207009 *does not* address the issue described in JDK-8208642. I was concerned that I wasn't building the JDK correctly and/or picking up the wrong JDK b

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-02 Thread Rory O'Donnell
That would be very useful, thanks. Rgds,Rory On 02/08/2018 10:31, Mark Thomas wrote: On 02/08/18 10:06, Rory O'Donnell wrote: Hi Mark, Your bug (JDK-8208642) has been closed as a duplicate of another issue : https://bugs.openjdk.java.net/browse/JDK-8207009 I will let you know when the fix

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-02 Thread Mark Thomas
On 02/08/18 10:06, Rory O'Donnell wrote: > Hi Mark, > > Your bug (JDK-8208642) has been closed as a duplicate of another issue : > > https://bugs.openjdk.java.net/browse/JDK-8207009 > > I will let you know when the fix get's into a build. Thanks Rory. I should be able to build jdk11 from sourc

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-02 Thread Rory O'Donnell
Hi Mark, Your bug (JDK-8208642) has been closed as a duplicate of another issue : https://bugs.openjdk.java.net/browse/JDK-8207009 I will let you know when the fix get's into a build. Rgds,Rory On 01/08/2018 10:47, Rory O'Donnell wrote: Thanks Mark, I'll follow up and advise when it's move

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-01 Thread Rory O'Donnell
Thanks Mark, I'll follow up and advise when it's moved into JBS Rgds,Rory On 01/08/2018 10:41, Mark Thomas wrote: Rory, I can confirm that there is a JDK bug here. The short version is that server initiated renegotiation of a TLSv1.2 connection fails if the Java client is configured to allow

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-08-01 Thread Mark Thomas
Rory, I can confirm that there is a JDK bug here. The short version is that server initiated renegotiation of a TLSv1.2 connection fails if the Java client is configured to allow TLSv1.3 Details available under internal review ID : 9056398 As always, I'm happy to provide further details if requ

JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-07-31 Thread Mark Thomas
On 31/07/18 15:19, Rory O'Donnell wrote: > Hi Mark, > > Does the latest JDK 11 EA build 24 also fail ? If yes, could you log a > bug as we are now > > in Rampdown Phase 2. > > Thanks,Rory I do see the failure with JDK 11 EA build 24 as well. I'm looking at this now. My instinct is that this is

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-07-31 Thread Rory O'Donnell
Hi Mark, Does the latest JDK 11 EA build 24 also fail ? If yes, could you log a bug as we are now in Rampdown Phase 2. Thanks,Rory On 31/07/2018 15:10, Mark Thomas wrote: On 17/07/18 12:26, Rory O'Donnell wrote: *JDK 12 Early Access  Build 02 is available at **http://jdk.java.net/12/*

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-07-31 Thread Mark Thomas
On 17/07/18 12:26, Rory O'Donnell wrote: > *JDK 12 Early Access  Build 02 is available at **http://jdk.java.net/12/* I've just run the Tomcat 9 test suite with the JDK 12 EA4 build and I see a few TLS related failures: [concat] Testsuites with failed tests: [concat] TEST-org.apache.tomca

JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

2018-07-17 Thread Rory O'Donnell
Hi Mark, *JDK 11 is in Rampdown Phase one* * *The overall feature set is frozen. No further JEPs will be targeted to this release.* * *Rampdown Phase two is scheduled to start * *26th of July* **JDK 11 EA build 22 , *under both the GPL and Oracle EA licenses, is now available at **