[
https://issues.apache.org/jira/browse/CASSANDRA-17580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538947#comment-17538947
]
David Capwell commented on CASSANDRA-17580:
-------------------------------------------
[~e.dimitrova] pointed out that this patch doesn't work on j9+ due to
modules... I am trying to review the JDK startup logic but it seems that there
really are not good hooks for this, so seems that the documented way to handle
this was broken by modules (unless you force exporting the module like we do so
many others..)...
Given that local JMX is most likely the most common case, unless we can handle
that I don't see the benefit of this patch... will keep trying to find a
solution but blocked for now
> 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: 0.5h
> 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: [email protected]
For additional commands, e-mail: [email protected]
