Perfect, thank you for the update!
On Wed, Feb 13, 2019 at 5:58 AM Ilya Kasnacheev
wrote:
> Hello!
>
> For TLSv1.2 on Windows the fix is ready and tests are running for it. Hope
> that it will be integrated soon.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 12 февр. 2019 г. в 20:46, Loredana
Hello!
For TLSv1.2 on Windows the fix is ready and tests are running for it. Hope
that it will be integrated soon.
Regards,
--
Ilya Kasnacheev
вт, 12 февр. 2019 г. в 20:46, Loredana Radulescu Ivanoff :
> Thank you very much for the info, it was very helpful.
>
> I assume it worked on Linux
Thank you very much for the info, it was very helpful.
I assume it worked on Linux because I specifically set TLS v1.2 as a JVM
argument, by specifying -Djdk.tls.server.protocols="TLSv1.2"
-Djdk.tls.client.protocols="TLSv1.2"
Would you be able to provide a (very) loose estimate for the fix? Is
Hello!
It seems that you have problems due not just one but two issues:
1) Java 11 has TLSv1.3 by default and Ignite does not support that -
https://issues.apache.org/jira/browse/IGNITE-11298
why it worked for you on CentOS is a mystery. For some reason by Ubuntu has
Java 10 in openjdk-11-jdk
Hello,
I would like to restart this topic because I can get a repro on Windows 10
with Java 11 and SSL enabled by starting two nodes using just the 2.7
Ignite distribution. I'm starting the Ignite nodes via ignite.bat, and I've
only added a few extra JVM options to allow Ignite to start with Java
Hello!
I have tried running SSL tests again and they seem to pass (only one test
fails for some different reason)
Can you try running those 2 nodes in stand-alone processes, see if problem
persists? I can see that you have SSL-enabled Tomcat running in same VM,
which I imaging could interfere
Hello!
I have tried to run the test with protocol "TLSv1.2", didn't see any
difference.
Regards,
--
Ilya Kasnacheev
ср, 24 окт. 2018 г. в 20:23, Loredana Radulescu Ivanoff :
> Hello again,
>
> I am working on getting the full SSL logs over to you, but I have one more
> question in between:
Hello again,
I am working on getting the full SSL logs over to you, but I have one more
question in between: TLS v1.3 is enabled by default in JDK 11, and my app
is using TLS v1.2 specifically. There's a known issue that's recently
addressed by the JDK related to TLS v1.3 half close policy,
Hello!
I would suggest regular (or DEBUG) Ignite logs + SSL debug logs.
https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html
Regards,
--
Ilya Kasnacheev
пт, 19 окт. 2018 г. в 20:58, Loredana Radulescu Ivanoff :
> Definitely - do you want debug logs, and if
Definitely - do you want debug logs, and if yes, should I enable them on
all Ignite packages, or just for certain ones? Any other diagnostic flags
that I should set?
On Fri, Oct 19, 2018 at 7:48 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Apache Ignite does not claim support JDK 11 at this moment.
Hello!
Apache Ignite does not claim support JDK 11 at this moment. However, I was
able to run SSL test (TcpDiscoverySslTrustedUntrustedTest) and it turned
out mostly fine.
More info is needed from your side, such as full instances logs.
Regards,
--
Ilya Kasnacheev
пт, 19 окт. 2018 г. в 0:56,
Hello
I think that the only supported version is Java 8 right now, and Java 11
support should come with 2.7 or 2.8 release.
https://issues.apache.org/jira/browse/IGNITE-8441
Cheers
Gianluca
Il giorno gio 18 ott 2018 alle ore 23:56 Loredana Radulescu Ivanoff <
lradu...@tibco.com> ha scritto:
>
Hello,
I can consistently reproduce this issue with Ignite 2.6.0, JDK 11 and SSL
enabled:
- the second node that I bring up joins, and then shortly after freezes
and prints this message every minute:
"WARN ...[*Initialization*]
processors.cache.GridCachePartitionExchangeManager: Still
13 matches
Mail list logo
