|Oracle® Enterprise Manager Getting Started with Oracle Fusion Middleware Management
11g Release 1 (188.8.131.52)
Part Number E17558-05
This chapter provides an overview of JVM Diagnostics. It contains the following sections:
Mission critical Java applications often suffer from availability and performance problems. Developers and IT administrators spend a lot of time diagnosing the root cause of these problems. Many times, the problems occurring in production environments either cannot be reproduced or may take too long to reproduce in other environments. This can cause severe impact on the business.
Oracle Enterprise Manager Grid Control 11g R1's JVM Diagnostics enables administrators to diagnose performance problems in Java application in the production environment. By eliminating the need to reproduce problems, it reduces the time required to resolve these problems. This improves application availability and performance. Using JVM Diagnostics, administrators will be able identify the root cause of performance problems in the production environment without having to reproduce them in the test or development environment. It does not require complex instrumentation or restarting of the application to get in-depth application details. Application administrators will be able to identify Java problems or Database issues that are causing application downtime without any detailed application knowledge. The key features of JVM Diagnostics are:
JVM Diagnostics provides in-depth monitoring of Java applications without slowing them down. It helps you to identify the slowest requests, slowest methods, requests waiting on I/O, requests using a lot of CPU cycles, and requests waiting on database calls. It also identifies the end-user requests that have been impacted by resource bottlenecks. Application resources that are causing the performance bottleneck are also visible.
JVM Diagnostics provides immediate visibility into the Java stack. You can monitor thread states and Java method/line numbers in real time and you can proactively identify issues rather than diagnosing issues like application crashes, memory leaks, and application hangs after they occur.
If a particular request is hanging or if the entire application is slow, administrators can perform a real-time transaction trace to view current Java application activity. You can see the offending threads and their execution call stacks. You can also analyze various bottleneck resources such as how much time a thread spent in waiting for a database lock. Complex problems such as activity in one thread (or request) affecting the activity in the other thread or rest of the JVM can be found very quickly.
Sometimes the monitoring interval (normally 10 seconds) that is in use is too coarse grained. The Java thread of interest may be too short lived or the amount of monitoring data collected may be insufficient. In such cases, you can run a JVM Trace to get fine-grained details of the JVM activity. This feature allows you to monitor your Java application at a very high frequency (default of once every 50ms) for a short period of time. This allows you to identify interdependency of threads, bottleneck resources (DB, I/O, CPU, Locks, Network) & top methods.
JVM Diagnostics facilitates tracing of Java requests to the associated database sessions and vice-versa enabling rapid resolution of problems that span different tiers. It highlights the slowest SQL queries and helps administrators to tune SQL and the database to improve the performance application. This facilitates smooth communication between the database administrators and application administrators by isolating the problems to the database or the application tier.
Memory leaks lead to application slowdowns and eventually cause applications to crash. JVM Diagnostics alerts administrators on abnormalities in Java memory consumption. Administrators can use JVM Diagnostics and take heap dumps in production applications without disturbing the application. They can take multiple heap dumps over a period of time, analyze the differences between the heap dumps and identify the object causing the memory leak. Heap analysis can be performed even across different application versions. Differential Heap Analysis with multiple heap dumps makes it easy to identify memory leaks.
JVM Diagnostics allows administrators to group sets of JVMs together into JVM pools. This provides the console user with a single view across all related JVMs. Hence all JVM's that make up a single application or a single cluster may be grouped together in an application. This allows administrators to visualize problems naturally and intuitively.
With JVM Diagnostics, you can perform real-time and historical diagnostics on your Java applications. This provides you with detailed insight on the root causes of production problems without having to reproduce the same problem in a Test or QA environment. You can play back transactions interactively from the browser and view the time spent in the network and the server. You can also view the response time breakdown by Servlet, JSP, EJB, JDBC, and SQL layers.
Apart from the real-time data, you can also analyze historical data to diagnose problems that occurred in the past. You can view historical data that shows the time taken by end-user requests and the breakdown by Servlet, JSP, EJB, JDBC, and SQL layers.
This section lists the new JVM Diagnostics features in Oracle Enterprise Manager Grid Control 11g R1.
JVM Diagnostics is now integrated with Oracle Enterprise Manager Grid Control.
Some of the pages in the old console have been converted to the ADF format.
The Enterprise Manager repository is now used for JVM Diagnostics.
Enterprise Manager Grid Control users can now perform JVM Diagnostics tasks depending on their privileges.
Secure communication between JVM Diagnostics Manager and Agent is now supported.
The features listed in this section are available only if you have applied the one-off patch.
Multiple JVM Diagnostics Managers: You can now deploy multiple JVM Diagnostics Managers and connect one or more agents to these managers. For more details, refer to the Scaling Out by Deploying Multiple JVM Diagnostics Managers section.
Level Zero (L0) Tracing: If the Application Dependency and Performance Agent is running and Request Monitoring has been configured, additional data is displayed in the JVM Diagnostics screens. For example, you may see:
Average Age on Top Requests for Domain (Pool) Summary page. Click a Request Name to view the request flow details.
In the Domain (Pool) or Real Time Analysis page, the Age, ECID, and RID is also displayed.
SQL Identifier Support - You can now perform queries and search for a SQL ID corresponding to a particular SQL text or SQL hash value.
Application Development Framework (ADF): With ADF support, entity objects and view objects are also displayed in the top metrics section
web.xml File: You now have an option to modify the
web.xml file for the JVM Diagnostics Agent. For details, see Download Agent Page.
The JVM Diagnostics Manager is supported on:
Windows (2000 or later)
Linux x86 (RHEL 3 or later)
Solaris SPARC (8 or later)
The JVM Diagnostics Database Agent supports Oracle 8i or later on the following platforms:
Linux x86, Linux x86_64 and IA64
Solaris SPARC and x86
HPUX 11 on PA-RISC and IA64
The JVM Diagnostics Agent supports the following JVMs:
Sun JDK - 1.3, 1.4, 1.5, and 1.6
JRockit - 1.4, and 1.5
HP JVM - 1.4, 1.5, and 1.6
IBM JVM - 1.4, 1.5, and 1.6
See the My Oracle Support site for the latest certification details.
We recommend that you use Sun JDK 1.6.0_18 32-bit for the JVM Diagnostics Manager.
You can use 64-bit JVM for the JVM Diagnostics Agent.
To use JVM Diagnostics, you must have either of the following Enterprise Manager system privileges:
JVM Diagnostics User: Allows you to view JVM Diagnostics data.
JVM Diagnostics Administrator: Allows you to manage JVM Diagnostics operations.
You can define these privileges in the Setup pages. For more details on defining these privileges, see the Enterprise Manager Security chapter in the Administration Guide.