Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exceptions annotation #17

Open
wsargent opened this issue Sep 28, 2017 · 0 comments
Open

Exceptions annotation #17

wsargent opened this issue Sep 28, 2017 · 0 comments

Comments

@wsargent
Copy link

wsargent commented Sep 28, 2017

If an operation throws an exception, then the JMX wrapper assumes that this is a failure to invoke:

javax.management.ReflectionException: Can't convert signature for operation checkHealth

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:

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
moonrumble pushed a commit to moonrumble/JMXWrapper that referenced this issue Jul 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant