[
https://issues.apache.org/jira/browse/CASSANDRA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602571#comment-17602571
]
Ekaterina Dimitrova edited comment on CASSANDRA-17668 at 9/9/22 10:29 PM:
--------------------------------------------------------------------------
Great! Let me know if you have any questions. Also, not sure whether you know
about
[Butler|https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-trunk/trunk],
you can consult it together with Jira(in case there was already a ticket
opened but not linked in Butler yet). It shows a history of the latest test
failures per branch(I shared the link for trunk) and you can click on the links
to check the actual error in Jira for the respective run.
was (Author: e.dimitrova):
Great! Let me know if you have any questions. Also, not sure whether you know
about
[Butler|https://butler.cassandra.apache.org/#/ci/upstream/compare/Cassandra-trunk/trunk],
you can consult it together with Jira(in case there was already a ticket
opened but not linked in Butler yet). It shows a history of the latest test
failures and you can click on the links to check the actual error in Jira for
the respective run.
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
