[
https://issues.apache.org/jira/browse/CASSJAVA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17943185#comment-17943185
]
Marcel commented on CASSJAVA-96:
--------------------------------
We are still tracking down the issue on our side. It seems that the behavior of
the 4.19.0 Cassandra Java driver is different from the 4.17.0 Datastax Java
driver when dealing with connections to a cluster.
We started with the 4.17.0 Datastax driver and a cluster that had SSL
configured but not enforced. Both ports 9042 and 9142 were reachable.
Our application connected fine to the Datastax DSE 6.8.53 cluster throwing no
execptions concerning the connection or SSL on the connection.
Then we switched the driver to the 4.19.0 Cassandra driver leaving the
application and the cluster as they were and we started to see channel
connection failures on the 9042 port which we had not configured in any contact
point for the CqlSession.
Digging into the issue on cluster and application side revealed, that the
cluster was not enforcing SSL and the application had not configured a SSL
context and the keystore/certs for the context. In addition the 9042 port was
still configured for connections on the cluster which we also changed. The
firewall should be blocking the connections anyways.
We are currently testing with the 4.17.0 Datastax driver and SSL context
configured the connection to the cluster which is enforcing SSL. So far this
looks good. Next we will switch again to the 4.19.0 Cassandra driver and
retest. A primlimary test yesterday also looked good.
So the question remains how is the 4.17.0 Datastax driver able to connect to
the 9142 (which is usually the SSL port) and the 4.19.0 Cassandra driver throws
warnings of channel connection failures trying to connect to the 9042 port?
> Driver throws warning on nodes not configured
> ---------------------------------------------
>
> Key: CASSJAVA-96
> URL: https://issues.apache.org/jira/browse/CASSJAVA-96
> Project: Apache Cassandra Java driver
> Issue Type: Bug
> Components: Core
> Reporter: Marcel
> Priority: Normal
>
> I have recently switched our application from the datastax 4.17.0 java driver
> to the Cassandra 4.19.0 java driver. I kept the configuration as before and
> had no issues using the driver locally on a docker single node instance of
> datastax. However when I use the new driver with our production datastax
> cluster with three nodes I get warnings:
> {code:java}
> [s0|/xxx.xxx.xxx.xxx:9042] Error while opening new channel
> (ConnectionInitException: [s0|connecting...] Protocol initialization request,
> step 1 (STARTUP {CQL_VERSION=3.0.0, COMPRESSION=lz4, DRIVER_NAME=Apache
> Cassandra Java Driver, DRIVER_VERSION=4.19.0,
> CLIENT_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}): failed to send request
> (java.nio.channels.NotYetConnectedException)) {code}
> On the cluster we use SSL connections configured on port 9142. These are also
> the only ports that the CQLSession is configured to connect to via
> addContactPoints().
> Is there something I need to change in the configuration?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
