Application Profiler
Use
The necessity of a quick trace without having to set up the Virtual Machine (VM) in debug mode, restart the container, or redeploy the application is frequently proven. Application profiling aims to provide application developers with a high-level, powerful tool for on-the-fly debugging of J2EE applications. Application profiling can be used to track an application’s performance. Arguments and the return value of an invocation can also be displayed.
This profiling can be used when the system administrator finds out that the requests to an application are too slow. The suspected application is started in profiling mode and all method invocations are tracked.
Application profiling works only with one Java server node, so if the system has more than one Java server node, only one has to be chosen. The application has an option of opening a new browser with the selected application and all requests from this browser are redirected to the selected server node.
The possible activities for you when using the application profiler are:
● Browse package structure of the application and view invocation data for all packages, classes and methods in the application
● Filter the application methods by net time, average net time, gross time and number of method invocations. These times are accumulated values of all invocations for the selected method. (Gross time is total time of the method invocation and net time is total time minus time of the all internal methods)
● View all invocations for a package, class or method in the application. Sorting and filtering are possible. For a selected invocation the whole invocation stack can be opened.
● For a selected invocation the return value, arguments and this pointer can be inspected.
See also:
Working with the Profiled Data