[
https://issues.apache.org/jira/browse/CASSANDRA-17638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539686#comment-17539686
]
Ekaterina Dimitrova commented on CASSANDRA-17638:
-------------------------------------------------
[~dcapwell] do you mind to review? You already saw the initial version plus you
are familiar with the problems/solutions.
One notable change is this one to be carefully verified. -
https://github.com/ekaterinadimitrova2/cassandra/pull/200/commits/ddf4d1ceacf047fc2867c9e8d688e507a3b3d33a#diff-9a49417aa0801ae88678da70e5e9fee41b7d5977217252059b4f5aa886941f32L232-R250
> Clients using JMX are unable to handle non-standard java types but we leak
> this into our Exceptions
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17638
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17638
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1-beta, 4.1.x, 4.x
>
>
> This is follow up ticket on CASSANDRA-17527 and CASSANDRA-17580.
> CASSANDRA-17580 was decided to be a backup non-default option for users who
> want to be 100% sure there are no leaked Cassandra exceptions. In that sense
> I will fix here all known ConfigurationExceptions that need to be thrown as
> IllegalArgumentException for the default behavior as we were always supposed
> to do that.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
