[
https://issues.apache.org/jira/browse/CASSANDRA-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518153#comment-17518153
]
Ekaterina Dimitrova commented on CASSANDRA-17527:
-------------------------------------------------
e had a discussion with David last night regarding the exceptions. It seems
there is a way to use non-default MBean interceptor to solve all our issues.
David came up with the idea. If that doesn't work or it is too much work,
changing ConfigurationExceptions to IllegalArgumentExceptions should work (in
the new methods suggested). Then we also need to whitelist it in the new test
too.
> Clients using JMX are unable to handle non-standard java types but we leak
> this into our interfaces
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17527
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/JMX
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> JMX clients only work if-and-only-if they have the same types defined by the
> interface, so non-standard java (or javax) types should never be used; we
> currently rely on humans to block this in review, which has lead to a few
> interfaces exposing Cassandra types
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
