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/09/07 15:50:00 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=17601369#comment-17601369 ]
Ekaterina Dimitrova edited comment on CASSANDRA-17668 at 9/7/22 3:49 PM:
-------------------------------------------------------------------------
Thanks, I just pushed it rebased with the last 6 commits from trunk into Jenkins. (a few days passed, sorry about that)
There is a limit on number of Jenkins dev runs in parallel which is currently reached so it will take time to start but it should be #1913 [here|https://jenkins-cm4.apache.org/view/patches/job/Cassandra-devbranch/]
was (Author: e.dimitrova):
Thanks, I just pushed it rebased with the last 6 commits from trunk into Jenkins.
There is a limit on number of Jenkins dev runs in parallel which is currently reached so it will take time to start but it should be #1913 [here|https://jenkins-cm4.apache.org/view/patches/job/Cassandra-devbranch/]
> 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
> Assignee: Leonard Ma
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org