[jira] [Created] (CASSANDRA-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them

["Ekaterina Dimitrova (Jira)" <ji...@apache.org>]

Ekaterina Dimitrova created CASSANDRA-17668:
-----------------------------------------------

             Summary: Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
                 Key: CASSANDRA-17668
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17668
             Project: Cassandra
          Issue Type: Bug
            Reporter: Ekaterina Dimitrova


This is a continuation of CASSANDRA-17638 where we fixed leaks introduced during development of 4.1 to ensure no regressions.

This ticket is to fix a few leakages which are there since previous major versions, not 4.1 regressions. 

{_}setRepairSessionMaxTreeDepth{_}(exists since 3.0) and _setRepairSessionSpaceInMegabytes(since 4.0)_

 in the DatabaseDescriptor. 

checkValidForByteConversion and _validateMaxConcurrentAutoUpgradeTasksConf (both since 4.0)_

 are used in both setters and on startup. They shouldn't throw ConfigurationException in the setters. 

There might be more but those are at least a few obvious I found in the DatabaseDescriptor.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org