[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508959#comment-17508959
]
Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:11 PM:
-----------------------------------------------------------------------
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
Basically, if my understanding is right, the test is running cqlsh to describe
namespace and uses ssl options specifying the certificate so I assume it
connects to the node started by the test via ssl.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers', {'127.0.0.1:9042':
ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal
error (_ssl.c:2635)')})` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
was (Author: maulin.vasavada):
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers', \{'127.0.0.1:9042':
ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal
error (_ssl.c:2635)')})` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
> Support Java 17
> ---------------
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]