JMX Monitoring Tools


What is JMX Monitoring?

JMX Monitoring Tools is done by asking for data from "Managed Beans" (MBeans) that are exposed through the JVM port (JMX console). MBean represents the resources that run within the JVM and provides data about the configuration and use of that resource. MBeans are usually grouped into "domains" to show where the resources are. Usually in JVM you will see many domains. For example, for applications running on male cats will see the domain "Catalina" and ".

Lang" represents the same thing for JVM run-time (e.g. Hotspot). You might also see the application's specific domain, given how simple it is to write special MBeans through the JMX interface. The big problem today in managing application performance is that each application is unique and different. Some applications are small and require low resources, while others are large and require significant resources. 

While application code is often optimized during the development cycle, little can be said for run-time and JVM containers. Yes, many organizations can resize memory stacks, or maybe garbage collection - but many will only use their applications with default configuration. Most of the time this is fine; however, as will be seen with the customer example below, JVM / container configuration can often be the main cause of slow performance because there are not enough resources available for the application with JMX Monitoring Tools.

Database Connection Pool Barriers

Examples of this come from customers recently who broke the main obstacles in their application and really showed the power of JMX applications and monitoring in action. Customers on this occasion have identified that the "Retrieve Carrier" business transaction takes more than 40 seconds to complete. In the screenshot below, you can see how individual business transactions are carried out through infrastructure. Note specifically that 38 seconds are spent accessing the "OracleDB1" database. 

At this stage, it might assume it's just a slow SQL statement that requires one or two indexes. If we go deeper into the JVM "ws" that call "OracleDB1," we can see the main hotspot responsible for this response time is the Spring BeanPersistanceTarget factory: findAdminlevelCarriers which makes several JDBC calls. If we then browse this JDBC activity, we can see the JDBC call that was made and we can see that 19.2 seconds is spent on "Get Pooled Connection in JMX Monitoring Tools.

We can confirm this connection bottleneck pool by looking at the screenshot below, which shows a metric from the JMX JVM console that displays the utilization of the database connection set up by the application. The green line on the chart shows the number of maximum database connections allowed (50), while the blue line shows the number of active database connections that the application starts from time to time. 

Download JMX Monitoring Tools

JMX Monitoring
Free Driver

See that sometimes the number of active connections is equal to the maximum number of connections allowed, when this happens a business transaction must wait until the connection is released. This is why some business transactions "Retrieve Carrier" wait 20 seconds for database connections and other transactions do not. 

In this case, the customer increases the size of the collection of database connections to 75, which completely removes this bottleneck. This is just a simple example of how combined JMX applications and monitoring can help organizations find the root cause of application performance problems. However, monitoring JMX itself only tells half of the story. 

Without monitoring the application, it will be blind to the impact of the business and understand what business transactions and specific application codes are tiring JVM resources. Get started for free today by downloading AppDynamics Lite 2.0, which provides JMX applications and monitoring for one JVM. Request a free 30 day trial of AppDynamics Pro, which provides more powerful features for managing performance across distributed applications in JMX Monitoring Tools.

Incoming search terms:

  • SNMP Port
  • PRTG Network Monitor
  • PRTG Download
  • Network Monitoring
  • SNMP Download
  • Mib Monitoring
  • Montoring Tools
  • SNMP Trap Download

Discussion: