By design mbeans must handle their own concurrency, as many threads can be accessing them. Dynamic mbeans can alter their mbean interface dynamically, e.g. now they report 3 attributes and 2 operation, then next moment 5 attributes and 4 operations, although this is not very common. Conceptually, the mbean would report a single MBeanInfo, at any given point in time, in practise, you can alter the reported mbeaninfo even for concurrent requests, but this is certainly a sick thing to do. Dynamic mbeans are really meant for adapting their interface to a particular backend/resource upon creation, plus they are supposed to be a little faster (no reflective calls), but harder to code. They are not meant for changing their interface every millisecond. I think you should start the other way round. What you want to do? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4119122#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...