You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where it may actually be a listed exception, as defined in the "exceptions" descriptor for the MBeanOperationInfo:
The class names of the exceptions that can be thrown when invoking a constructor or operation, or getting an attribute. The meaning of this field is defined by this specification but the field is not set or used by the JMX API itself. Exceptions thrown when setting an attribute are specified by the field setExceptions.
Exceptions declared here should be passed through without nesting.
i.e. a JMRuntimeException exception with a message
Caused by: javax.management.JMRuntimeException: All host(s) tried for query failed (tried:
/192.168.99.100:9042
com.datastax.driver.core.exceptions.TransportException: [/192.168.99.100:9042] Cannot connect
The text was updated successfully, but these errors were encountered:
moonrumble
pushed a commit
to moonrumble/JMXWrapper
that referenced
this issue
Jul 5, 2019
If an operation throws an exception, then the JMX wrapper assumes that this is a failure to invoke:
https://github.com/uklimaschewski/JMXWrapper/blob/master/src/com/udojava/jmx/wrapper/JMXBeanWrapper.java#L454
Where it may actually be a listed exception, as defined in the "exceptions" descriptor for the
MBeanOperationInfo
:Exceptions declared here should be passed through without nesting.
i.e. a JMRuntimeException exception with a message
The text was updated successfully, but these errors were encountered: