Re: JMX exposing non-standard java classes, to fix requires a breaking change

2022-05-05 Thread David Capwell
-Dcassandra.settings.jmx_hide_non_java_exceptions=false Does anyone see any issues about this? > On Apr 6, 2022, at 9:35 AM, David Capwell wrote: > > I noticed in DatabaseDescriptor there are setters that are leaking it to JMX > since cassandra-3.0. I am not sure whether we can just

Re: JMX exposing non-standard java classes, to fix requires a breaking change

2022-04-06 Thread David Capwell
have different understanding so I want to align us to ensure we > don’t break tools by fixing or not stuff… > In many setters we were actually not doing the same checks we do on > Startup too… I consider this being a bug. > > On Tue, 5 Apr 2022 at 18:21, David Capwell wrote: >

JMX exposing non-standard java classes, to fix requires a breaking change

2022-04-05 Thread David Capwell
There are 2 places that expose non-standard java classes, so JMX only works if and only if the JMX client also has Cassandra's jars, else they will fail; the 2 examples are org.apache.cassandra.service.StorageServiceMBean#enableAuditLog throws org.apache.cassandra.exceptions.ConfigurationException