On a project called Indy I am working on I've come across an issue running the com.datastax.cassandra:cassandra-driver-core:3.7.2 connector driver. The work I've been doing is to migrate Indy from JDK8 to JDK11. I have an open issue to investigate why the datastax Cassandra driver is throwing an exception when running on JDK11.
I've got to the point to raise this as an upstream issue.
I notice that other users have come across the same issue. Switching back to JDK8 is the workaround for those users.
I'd like to suggest the com.datastax.cassandra:cassandra-driver-core project build system be adapted. To incorporate a Multi Release Jar. Permitting the jVM at runtime to load classes that allow Netty to probe the ability of the runtime and connect to Cassandra.
$ uname -a
Linux burtha-f31 5.6.19-200.fc31.x86_64 #1 SMP Wed Jun 17 16:54:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
baremetal. Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz.
I've looked at the issue you reported for your project and found that the Exception you see with regard to Netty:
Is really just a debug log indicating Netty won't be able to make use of some of its optimizations. See this:
I'm still looking into the initial issue you're having, but I don't think it is relates to that Netty debug log.
Some additional investigation reveals the JDK version running Cassandra is crucial. In my case switching the default jvm on the platform to JDK11 was the cause. The datastax connector only works with Cassandra 3.x running with JDK8. Cassandra only supports JDK11 with the 4.0 release.
I’m happy for this issue to be closed.
Thanks for the updates. Closing as requested.