You can monitor many performance statistics through the Admin Console user interface, through the command-line interface, through the stats-xml URI, and through perfdump. For all these monitoring methods, the server uses the statistics it collects. None of these monitoring methods will work if statistics are not collected.
The statistics give you information at the configuration level, the server instance level, or the virtual server level. The statistics are broken up into functional areas.
Java Virtual Machine (JVMTM)
Session Threads, including Profiling data (available if profiling is enabled)
Java DataBase Connectivity (JDBCTM) (available if a JDBC resource is created and the connection pool is accessed)
For the virtual server, statistics are available in the following areas:
Profiling Data (available if profiling is enabled)
Servlet and Servlet Response Cache (available if the Servlet cache is enabled in sun.web.xml)
Some statistics default to zero if Quality of Service (QoS) is not enabled, for example, the count of open connections, the maximum open connections, the rate of bytes transmitted, and the maximum byte transmission rate.
Statistics are activated by default on Web Server. However, if you have disabled them, you need to enable them again to monitor your server for performance. To enable statistics, use Admin Console or the wadm command-line utility (CLI).
Collecting statistics causes a slight hit to performance.
From the Admin Console Common Tasks page, select the configuration.
Click Edit Configuration.
Click the General tab.
Click the Monitoring Settings sub tab.
On the Monitoring Settings page, under General Settings, select the Statistics Enabled checkbox.
Configure the interval and profiling.
Restart the server.
Enter the following CLI command to enable statistics collection:
To disable statistics, set enabled to false.
To set the interval and enable profiling, use the set-stats-prop interval and profiling properties. For more information, see the help for set-stats-prop.
Restart the server.