Conclusion
The JBoss server uses JMX both to enable service management and to build a loosely coupled infrastructure for the server-side components. In the 2.x series the JBoss server introduced an interceptor-based approach to implementing an EJB container functionality. In the 3.x series this same approach has been generalized at the JMX level, enabling any service implementation to take advantage of the invocation interceptors.
The JMX MBean server provides a dynamic view to the server where new services may be added, removed, or restarted at runtime. As such, the MBean server has become the core of the JBoss general-purpose service architecture, decoupling the service implementations from each other and acting as a central invocation bus between components. The JBossMX implementation has been optimized for speed in the invocation chain, catering to the requirements of a high-performance J2EE application server. In addition, the JBossMX implementation provides the possibility of customizing MBean invocation behavior via interceptors, enabling a 24x7 availability for all service implementations.