[
https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531789#comment-17531789
]
Ekaterina Dimitrova commented on CASSANDRA-17580:
-------------------------------------------------
Marking 4.1.x as per
[https://lists.apache.org/thread/wo3o86ntpg59r4fy2qhsh1j6fgntxf67,] confirmed
with PMC
> 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.x
>
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
