[jira] [Comment Edited] (CASSANDRA-17580) Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions

["Ekaterina Dimitrova (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539029#comment-17539029 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-17580 at 5/18/22 7:33 PM:
--------------------------------------------------------------------------

Looking back into this, It introduces a new flag and it won't be the default fix, should we commit it only to trunk? Not sure


was (Author: e.dimitrova):
Looking back into this, I introduces new flag an it won't be the default fix, should we commit it only to trunk? Not sure

> 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
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 4.1-beta, 4.1.x
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org