Servlets
The servlet summary lists all servlets
that are running in the current application server. Use the servlet
summary view to quickly find the most time intensive servlets and
the applications that use them, and to determine which servlets are
invoked most often. You can sort the summary table by any of the columns.
Tips
- Sort by Avg Response Time to find the slowest servlet or
JavaServer Page (JSP).
- Sort by Total Requests to find the servlet or JSP used
the most.
- Sort by Total Time to find the most costly servlet or JSP.
Enterprise beans
The Enterprise JavaBeans (EJB) summary lists all enterprise
beans running in the server, the amount of time spent in their methods,
the number of EJB invocations, and the total time spent in each enterprise
bean.
total_time = number_of_invocations * time_in_methods
Sort
the various columns to find the most expensive enterprise bean. Also,
if the PMI counters are enabled for individual EJB methods, there
is a check box next to the EJB name that you can select to see statistics
for each of the methods.
Tips
- Sort by Avg Response Time to find the slowest enterprise
beam.
- Sort by Method Calls to find the enterprise bean used the
most.
- Sort by Total Time to find the most costly enterprise bean.
EJB methods
The EJB method summary shows statistics
for each EJB method. Use the EJB method summary to find the most costly
methods of your enterprise beans.
Tips
- Sort by Avg Response Time to find the slowest EJB method.
- Sort by Method Calls to find the EJB method used the most.
- Sort by Total Time to find the most costly EJB method.
Connection pools
The connection pool summary
lists all data source connections that are defined in the application
server and shows their usage over time.
Tip
- When the application is experiencing normal to heavy usage, the
pools used by that application must be nearly fully used. Low utilization
means that resources are being wasted by maintaining connections or
threads that are never used. Consider the order in which work progresses
through the various pools. If the resources near the end of the pipeline
are under used, it might mean that resources near the front are constrained
or that more resources than necessary are allocated near the end of
the pipeline.
Thread Pools
The thread pool summary shows
the usage of all thread pools in the application server over time.
Tip
- When the application is experiencing normal to heavy usage, the
pools used by that application must be nearly fully used. Low utilization
means that resources are being wasted by maintaining connections or
threads that are never used. Consider the order in which work progresses
through the various pools. If the resources near the end of the pipeline
are under used, it might mean that resources near the front are constrained
or that more resources than necessary are allocated near the end of
the pipeline.
PMI levels and counters required
In order
to view Tivoli® Performance
Viewer (TPV) summary reports, the minimum PMI level must be
enabled. Otherwise, you must use the custom monitoring level,
and enable the PMI level counters required for the specific report
you want to view.
Table 1. Required properties
for TPV summary reports. The TPV summary reports are generated
upon request and are not dynamically refreshed
Summary Report |
PMI level required |
Custom PMI counters required |
Servlets |
Basic |
Web Applications.RequestCount
Web Applications.ServiceTime
|
Enterprise beans |
Basic |
Enterprise Beans.MethodCallCount
Enterprise Beans.MethodResponseTime
|
EJB methods |
All |
WSEJBStats.MethodStats.MethodLevelCallCount
WSEJBStats.MethodStats.MethodLevelResponseTime
|
Connection pools |
Extended |
JDBC Connection Pools.PoolSize
JDBC Connection Pools.AllocateCount
JDBC Connection Pools.ReturnCount
|
Thread pools |
Extended |
Thread Pools.PoolSize
Thread Pools.ActiveCount
|