[ 
https://issues.apache.org/jira/browse/CASSANDRA-20372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17931378#comment-17931378
 ] 

Kapil Shewate commented on CASSANDRA-20372:
-------------------------------------------

JDK used is jdk17

> Cassandra5.0.2 service is not coming up after enabling JMX SSL
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-20372
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20372
>             Project: Apache Cassandra
>          Issue Type: Bug
>            Reporter: Kapil Shewate
>            Priority: Normal
>
> Starting Cassandra ... STARTED
> NOTE: Depending on cluster size, it may take a few minutes for Cassandra to 
> be ready.
>       Confirm node is operational by running 
> "/opt/install_dir/product_test/apache-cassandra/bin/nodetool status" before 
> starting other nodes.
> [root@in-r9-di-bgm01 bin]# JVMJ9VM007W Command-line option unrecognised: 
> -Xlog:gc=info,heap*=trace,age*=debug,safepoint=info,promotion*=trace:file=./../logs/gc.log:time,uptime,pid,tid,level:filecount=10,filesize=10485760
> WARNING: Jamm is starting with the UseEmptySlotsInSupers JVM option disabled. 
> The memory layout created when this option is enabled cannot always be 
> reproduced accurately by the Specification or UNSAFE strategies. By 
> consequence the measured sizes when these strategies are used might be off in 
> some cases.
> Exception (java.lang.ExceptionInInitializerError) encountered during startup: 
> null
> java.lang.ExceptionInInitializerError
>         at 
> java.base/java.lang.J9VMInternals.ensureError(J9VMInternals.java:216)
>         at 
> java.base/java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:205)
>         at 
> org.apache.cassandra.utils.JMXServerUtils.configureJmxAuthentication(JMXServerUtils.java:188)
>         at 
> org.apache.cassandra.utils.JMXServerUtils.createJMXServer(JMXServerUtils.java:106)
>         at 
> org.apache.cassandra.utils.JMXServerUtils.createJMXServer(JMXServerUtils.java:154)
>         at 
> org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:178)
>         at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:246)
>         at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:727)
>         at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:865)
> Caused by: java.lang.RuntimeException: java.lang.IllegalAccessException: 
> access to public member failed: 
> com.sun.jmx.remote.security.JMXPluggableAuthenticator.<init>[Ljava.lang.Object;@ee9954c3/invokeSpecial,
>  from class 
> org.apache.cassandra.utils.JMXServerUtils$JMXPluggableAuthenticatorWrapper 
> (unnamed module @11673ee7)
>         at 
> org.apache.cassandra.utils.JMXServerUtils$JMXPluggableAuthenticatorWrapper.<clinit>(JMXServerUtils.java:306)
>         ... 7 more
> Caused by: java.lang.IllegalAccessException: access to public member failed: 
> com.sun.jmx.remote.security.JMXPluggableAuthenticator.<init>[Ljava.lang.Object;@ee9954c3/invokeSpecial,
>  from class 
> org.apache.cassandra.utils.JMXServerUtils$JMXPluggableAuthenticatorWrapper 
> (unnamed module @11673ee7)
>         at 
> java.base/java.lang.invoke.MemberName.makeAccessException(MemberName.java:961)
>         at 
> java.base/java.lang.invoke.MethodHandles$Lookup.checkAccess(MethodHandles.java:3888)
>         at 
> java.base/java.lang.invoke.MethodHandles$Lookup.getDirectConstructorCommon(MethodHandles.java:4123)
>         at 
> java.base/java.lang.invoke.MethodHandles$Lookup.getDirectConstructorNoSecurityManager(MethodHandles.java:4117)
>         at 
> java.base/java.lang.invoke.MethodHandles$Lookup.unreflectConstructor(MethodHandles.java:3439)
>         at 
> org.apache.cassandra.utils.JMXServerUtils$JMXPluggableAuthenticatorWrapper.<clinit>(JMXServerUtils.java:302)
>         ... 7 more



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to