Connection Queue Information - Sun Microsystems Sun Java System Web Server 7.0 Manual

"Java Virtual Machine (JVM) Information" on page 70
■
"Web Application Information" on page 71
■
"JDBC Resource Information" on page 72
■
Once you have viewed the statistics you need, you can tune various aspects of your server's
performance at the configuration level using the Admin Console's Performance tab. The Admin
Console Performance tab includes settings for many performance categories, including:
HTTP Settings (includes Thread Pool and Keep Alive)
■
DNS Settings
■
SSL and TLS Settings
■
Cache Settings
■
CGI Settings
■
Access Log Buffer Settings
■
You can also view and set tuning parameters using the appropriate wadm commands. In general,
when you set tuning properties using wadm commands, the names of the properties are the same
as displayed in stats.xml.

Connection Queue Information

In Web Server, a connection is first accepted by acceptor threads associated with the HTTP
listener. The acceptor threads accept the connection and put it into the connection queue.
Then, request processing threads take the connection in the connection queue and process the
request. For more information, see
Connection queue information shows the number of sessions in the connection queue, and the
average delay before the connection is accepted by the request processing thread.
The following is an example of how these statistics are displayed in perfdump:
ConnectionQueue:
-----------------------------------------
Current/Peak/Limit Queue Length
Total Connections Queued
Average Queue Length (1, 5, 15 minutes)
Average Queueing Delay
The same information is displayed in a different format through the Admin Console or
command-line interface, with some slight differences. The following table shows the
information as displayed in the Admin Console when accessing monitoring information for the
server instance:
Chapter 2 • Tuning Sun Java System Web Server
"Connection-Handling Overview" on page
0/1853/160032
11222922
90.35, 89.64, 54.02
4.80 milliseconds
Using Monitoring Data to Tune Your Server
40.
49