Quantcast
Viewing all articles
Browse latest Browse all 12281

MBeans Discovery fails due to serialization exception.

So first of all let me preface this by saying I'm very new to JMX and MBeans in general.  I think I have uncovered a potential flaw in the way the MBeans discovery works.  If there is any MBean within a java class that throws an error the entire discovery for that class fails.  I was trying to use the discovery to find a specific MBean but kept getting errors.  I then opened it up in Java console and found the exact path and attribute I wanted to monitor and manually configured the component.  It took much longer simply because of a few failed MBeans prevented me from doing the discovery.  It would be better if SW would just ignore or mark out the MBeans that fail without causing the discovery of the class to completely fail.

 

I hope I'm describing this correctly.  aLTeReGo if you need any further information I'd be happy to do a session with someone to show the symptoms.  I'm on SAM 5.2


Viewing all articles
Browse latest Browse all 12281

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>