This should be fixed in JDK 11 b23. Please try again. See
https://bugs.openjdk.java.net/browse/JDK-8199779 for more info.
--Sean
On 6/25/18 12:28 AM, Jaikiran Pai wrote:
I couldn't locate this bug in the JIRA nor the bugs.java.net, to see if
it's acknowledged as an issue. So FWIW - I can repro
I couldn't locate this bug in the JIRA nor the bugs.java.net, to see if
it's acknowledged as an issue. So FWIW - I can reproduce this even on
MacOS (so it isn't just specific to Windows OS). This is the code:
import java.net.URL;
import java.io.InputStream;
public class CertTest {
public s
Thank you for response.
I submitted bug to bugtracker. Iinternal review ID : 9055666
Didn't find a way to attach files there, but program example is short and
can be easily run by anyone.
Andrey Turbanov.
2018-06-15 16:58 GMT+03:00 Sean Mullan :
> The 2nd (good) logfile looks like it is from a
The 2nd (good) logfile looks like it is from a completely different
program - are you sure you are using the same code?
If it is, please rerun again and also add -Djavax.net.debug=all to the
command-line which should give a bit more debug info as to where the
issue is occurring in the TLS hand
Please add -Djava.security.debug=certpath to the java command line and
attach the log file. Preferably, attach 2 log files, one for a good run
and one for a bad run. This should help show what the problem is.
--Sean
On 6/11/18 7:59 PM, Андрей Турбанов wrote:
Hello.
I tried to use early jdk11
