[
https://jira.jboss.org/jira/browse/JBAS-5933?page=com.atlassian.jira.plug...
]
Jay Howell commented on JBAS-5933:
----------------------------------
Yep you are correct. Sorry, After finding it in the RawDynamicInvoker, I searched through
the code to find any other occurances. I saw the exception message and just didn't
look good enough.
throw new RuntimeException("Cannot obtain MBeanInfo " + name, result);
Jay:)
JMX operations eat underlying exception
---------------------------------------
Key: JBAS-5933
URL:
https://jira.jboss.org/jira/browse/JBAS-5933
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.2.3.GA
Reporter: Jay Howell
Assignee: Dimitris Andreadis
Fix For: JBossAS-4.2.4.GA
Inside of both MBeanSeverImpl and the RawDynamicInvoker, exceptions are being eaten, when
the getMBeanInfo method is being called. The only thing thrown is the
NotCompliantMBeanException with a canned exception message. The underlying exception can
be anything from a classloader issue, to just a plain old CNF Exception. This code needs
to be changed so that the underlying exception is propagated out to be seen in the log.
the code is...
try
{
this.info = getMBeanInfo();
}
catch (Exception e)
{
throw new NotCompliantMBeanException("Cannot obtain MBeanInfo, for: " +
oname);
}
which just eats the underlying Exception.
This should be
try
{
this.info = getMBeanInfo();
}
catch (Exception e)
{
throw new NotCompliantMBeanException("Cannot obtain MBeanInfo, for: " +
oname, e);
}
And NotCompliantMBeanException should be chaned to take the nested exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira