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
Not critically important, but if you try and use the MBean exporter (org.springframework.jmx.export.MBeanExporter) to export a web services client (JaxWsPortProxyFactoryBean) then you get an NPE
MBeanExporter.adaptMBeanIfPossible() gets a null back from AopUtils.getTargetClass(), (probably right?)
then JmxUtils.getMXBeanInterface() tries to find the superclass of a null class.
Probably the getMXBeanInterface() should be made null safe?
AopUtils.getTargetClass(...) is actually supposed to always return a non-null Class. I've made this null-proof along with related pieces of code in JmxUtils.
So the MBean export should work in your case as well now. This fix will be available in tonight's 3.0.2 snapshot already; give it an early try if you got the chance!
Karl Palsson opened SPR-7011 and commented
Not critically important, but if you try and use the MBean exporter (org.springframework.jmx.export.MBeanExporter) to export a web services client (JaxWsPortProxyFactoryBean) then you get an NPE
MBeanExporter.adaptMBeanIfPossible() gets a null back from AopUtils.getTargetClass(), (probably right?)
then JmxUtils.getMXBeanInterface() tries to find the superclass of a null class.
Probably the getMXBeanInterface() should be made null safe?
Affects: 3.0.1
Referenced from: commits 296aa96
The text was updated successfully, but these errors were encountered: