About J2EE Diagnostics Monitoring - LoadRunner

The J2EE Diagnostics module monitor provides the following information for each transaction:

  • Average response time per method/query
  • Number of method calls per second
  • Breakdown information by layer, class, and method
  • Chain of calls and call stack statistics

With this level of detail, you can get an overview of the entire chain of activity within the system. At the same time, you can break down J2EE layers into classes and methods to enable you to pinpoint the exact location where time is consumed. You can also view the transaction call chai to track the percent of time spent for each part of the transaction. You can correlate the end user response time with the Web server activity (Servlets and JSPs data), application server activity (JNDI), and back-end activity of database requests (JDBC methods and SQL queries). You can also monitor a class that is of special interest to you by defining a custom layer. To enable the Diagnostics for J2EE to display custom classes or packages, you must set up the J2EE probe to monitor the classes and packages.

The J2EE Diagnostics monitor enables you to analyze J2EE component metrics during a scenario run by using an agent installed on the application server to collect information on the J2EE components. These measurements are sent from the application server back to the Controller through a channel contained in the J2EE Diagnostics monitor. The J2EE Diagnostics monitor supports the leading application servers, such as IBM WebSphere and BEA WebLogic.

Note: The J2EE Diagnostics module monitor requires MSXML 3.0 or later (included in Internet Explorer 6.0). You can install MSXML 3.0 from the Microsoft MSDN Web site.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

LoadRunner Topics