[CASSANDRA-17580] Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Open
Priority: Normal
Resolution: Unresolved
Fix Version/s: 5.x
Component/s: Legacy/Observability, Observability/JMX
Labels:
None

Complexity:
Low Hanging Fruit
Platform:

All
Impacts:

None
Test and Documentation Plan:

Hide

added tests

Show
added tests

Description

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.

Attachments

Issue Links

is related to

CASSANDRA-17638 Clients using JMX are unable to handle non-standard java types but we leak this into our Exceptions

Resolved

relates to

CASSANDRA-17527 Clients using JMX are unable to handle non-standard java types but we leak this into our interfaces

Resolved

links to

CI: trunk

PR: trunk

Activity

People

Assignee:: Stefan Miklosovic

Reporter:: David Capwell

Authors:: Stefan Miklosovic

Reviewers:: Brandon Williams, Ekaterina Dimitrova, Stefan Miklosovic

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 25/Apr/22 17:43

Updated:: 08/May/23 20:26

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

40m