You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/05/04 15:24:00 UTC

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Dimitrova updated CASSANDRA-17580:
--------------------------------------------
    Fix Version/s: 4.1.x
                       (was: 4.1)

> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org