Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices (e. g. printers) and service oriented networks. Those resources are represented by objects called MBeans (for Managed Bean). In the API, classes can be dynamically loaded and instantiated. Managing and monitoring applications are two most important usages of it.
JBoss relies on JMX to load in the MBean services that make up a given server instance’s personality. All of the bundled functionality provided with the standard JBoss distribution is based on MBeans. The best way to add services to the JBoss server is to write your own JMX MBeans. There are two classes of MBeans: those that are independent of JBoss services, and those that are dependent on JBoss services.
Here we will go through some very common and basic MBean related demos and samples like Creating our own custom MBeans using SAR (JBoss Specific Service Archive), MBean monitoring and management etc.
- Accessing JBoss MBeans to get DataSource details
- How to use Scheduler Service of JBoss for Job Scheduling?
- Monitoring Heap & NonHeap Memory of JBoss using MBean code
- Generating HeapDump while running JBoss as a Windows Service
- Listing & Deleting Messages from JMS Queue using JMX
- How to create a Service Archieve SAR file in JBoss AS6
- How to create a Service Archieve SAR file in JBoss AS7
- Using JAR file placed inside a SAR in JBoss AS7
- Getting WebService Statistics using JMX in JBoss AS7
- Listing All MBeans present inside JBossAS7 programatically
- Accessing “jboss.web:type=*” MBeans Programmatically in JBossAS7.1.1
- Expiring HttpSessions associated with a WebApp using JMX client in JBossAS7.1.1
- Accessing JBossAS7 HornetQ Related statistics using JMX remotely
- Creating and Registering MXBean in JBossAS7.1.1