[
https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529560#comment-17529560
]
Ekaterina Dimitrova commented on CASSANDRA-17580:
-------------------------------------------------
Old JMX endpoints also can throw Configuration exceptions in case of negative
value (those are now prohibited old/new config, considered a bug), as we
prohibit those in the constructors of the new types by throwing
ConfigurationException.
To me the borders around what needs to be in before a freeze and what before a
release is still not always clear.About this one I asked in Slack when we
discussed it, here is a link where I was asking [~mck] to confirm this is not a
freeze blocker -
https://the-asf.slack.com/archives/CK23JSY2K/p1650909124028529?thread_ts=1650899566.507359&cid=CK23JSY2K.
> Clients using JMX are unable to handle non-standard java types but we leak
> this into our Exceptions
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17580
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Observability, Observability/JMX
> Reporter: David Capwell
> Priority: Normal
> Fix For: 4.1
>
>
> This is an extension of CASSANDRA-17527.
> When we throw in JMX the exception gets serialized and sent over the wire,
> and if the client doesn’t have the same class path it fails and the exception
> is lost and replaced with a ClassNotFoundException. This is bad as the user
> has no idea what the issue is so unable to resolve it.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
