Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-17580

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

    XMLWordPrintableJSON

Details

    • Low Hanging Fruit
    • All
    • None
    • 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

          Activity

            People

              dcapwell David Capwell
              dcapwell David Capwell
              David Capwell
              Brandon Williams, Ekaterina Dimitrova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m