In my previous blog, we discussed how to locate MBeans within the custom tree.  We're going to piggy back that discussion and show how to purge an EHCache MBean by executing the removeAll() operation.

For reference, let's see the findMBean() helper method we defined previously:

My collegue Ron DiFrango recently wrote a blog about exposing custom MBeans within the WebLogic container.  Both Ron and myself experienced similar frustrations when trying to work with custom MBeans and his blog is a must read if you're having difficulty finding yours.

Once the container is setup as directed in Ron's blog, you'll quickly notice that several of WLST's APIs for navigating do not work in the custom tree; most notably is the find API.  The lack of a find API is especially troubling when you have MBeans such as ones for EHCache that use the memory location as part of the unique identifier, for example:

Eric Miles and I were working on different clients that were both utilizing the Weblogic application and the Spring framework.  Each of needed a way to expose some of the configuration items as JMX beans so that production support folks could change the values of these items at runtime without requiring server re-boots.  Because both of us were using Spring, exposing the beans was fairly straight forward, we just followed the Spring documentation for exporting JMX beans.