You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/05/27 18:32:00 UTC
[jira] [Updated] (CASSANDRA-17668) Fix leak of non-standard Java types in our Exceptions as clients using JMX are unable to handle them
[ https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ekaterina Dimitrova updated CASSANDRA-17668:
--------------------------------------------
Description:
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.
CC [~dcapwell]
was:
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.
> 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
> Components: Legacy/Observability, Observability/JMX
> Reporter: Ekaterina Dimitrova
> Priority: Normal
>
> 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.
> CC [~dcapwell]
--
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