DefaultVirtual Server

Virtualservers work using the HTTP 1.1 Host header. If the end user’sbrowser does not send
theHost header, or if the server cannot nd the virtual server specied by the Host header, Web
Serverhandles the request using a default virtual server. You can congure the default virtual
serverto send an error message or serve pages from a special document root.
Tuning
Thissetting is tunable when you edit an HTTP listener.
Keep-AliveInformation
Thissection provides information about the server’s HTTP-levelkeep-alive system.
Note– The name keep alive should not be confused with TCP keep-alives. Also, note that the
namekeep-alive was changed to PersistentConnections in HTTP 1.1, but Web Server
continuesto refer to them as keep-alive connections.
Thefollowing example shows the keep-alive statistics displayed by perfdump:
KeepAliveInfo:
--------------------
KeepAliveCount 198/200
KeepAliveHits 0
KeepAliveFlushes 0
KeepAliveRefusals 56844280
KeepAliveTimeouts 365589
KeepAliveTimeout 10 seconds
Thefollowing table shows the keep-alive statistics displayed in the Admin Console:
TABLE2–3 Keep-AliveStatistics
Numberof Connections Processed 0
TotalNumber of Connections Added 198
MaximumConnection Size 200
Numberof Connections Flushed 0
Numberof Connections Refused 56844280
Numberof Idle Connections Closed 365589
UsingMonitoringData to TuneYour Server
Chapter2 • Tuning Sun Java System Web Server 53