Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the proper exception handling strategy for MBean operations? Some of these operations can fail (e.g. drop a user who isn’t connected) and an exception should be reported, but I don’t know how my exceptions can percolate up to the JMX layer. My best idea is C-style return codes.
That’s the intent of javax.management.MBeanException, which is declared as thrown from MBeanServerConnection.invoke. To quote from the JavaDoc:
So rather than return cryptic integer codes, (or BigDecimal if the bigger the better 😉 ) just trap the “business exception”, create a new MBeanException using the business exception and throw it. Provided your business exception is serializable and present in the classpath of the caller, the caller should be able to unwrap the JMX exception and get to the business exception.
If either of those assumptions is not true, just create a message based on the business exception class name and message and create an MBeanException from a new Exception (so you get a stack trace) and your new error message.