I have added below script in cassandra-env.sh and restarted cassandra, still issue not fixed
JVM_OPTS="$JVM_OPTS -Dcom.sun.jndi.rmiURLParsing=legacy"
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
I have added below script in cassandra-env.sh and restarted cassandra, still issue not fixed
JVM_OPTS="$JVM_OPTS -Dcom.sun.jndi.rmiURLParsing=legacy"
This issue is a duplicate of question #13764 where I've explained the workaround.
The issue relates to clients such as nodetool
which needs to switch to legacy parsing to get around the stricter rules for RMI URLs. The keyword in my statement above being "clients". You've applied the workaround on the server but the issue affects clients, not server.
Also, it is not a fix -- just a temporary workaround. The issue has been fixed in Cassandra 3.0.27, 3.11.13, 4.0.4 and 4.1 by CASSANDRA-17581. You will need to upgrade to the latest supported version to get the fix. Cheers!
7 People are following this question.
DataStax Enterprise is powered by the best distribution of Apache Cassandra ™
© 2022 DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.
Privacy Policy Terms of Use