Default Virtual Server
Virtual servers work using the HTTP 1.1 Host header. If the end user's browser does not send
the Host header, or if the server cannot find the virtual server specified by the Host header, Web
Server handles the request using a default virtual server. You can configure the default virtual
server to send an error message or serve pages from a special document root.
Tuning
This setting is tunable when you edit an HTTP listener.
Keep-Alive Information
This section provides information about the server's HTTP-level keep-alive system.
The name keep alive should not be confused with TCP keep-alives. Also, note that the
Note –
name keep-alive was changed to PersistentConnections in HTTP 1.1, but Web Server
continues to refer to them as keep-alive connections.
The following example shows the keep-alive statistics displayed by perfdump:
KeepAliveInfo:
--------------------
KeepAliveCount
KeepAliveHits
KeepAliveFlushes
KeepAliveRefusals
KeepAliveTimeouts
KeepAliveTimeout
The following table shows the keep-alive statistics displayed in the Admin Console:
Keep-Alive Statistics
TABLE 2–3
Number of Connections Processed
Total Number of Connections Added
Maximum Connection Size
Number of Connections Flushed
Number of Connections Refused
Number of Idle Connections Closed
Chapter 2 • Tuning Sun Java System Web Server
198/200
0
0
56844280
365589
10 seconds
Using Monitoring Data to Tune Your Server
0
198
200
0
56844280
365589
53
Need help?
Do you have a question about the Sun Java System Web Server 7.0 and is the answer not in the manual?
Questions and answers