Tuning
Youcan tune the maximum number of connections that the server allows to wait at one time
beforeclosing the oldest connection in the Admin Console by editing the Maximum
Connectionseld on the conguration's Performance tab ⇒HTTP tab, under Keep Alive
Settings.The default is 200. In the command-line interface, use the max-connections property
inthe wadm set-keep-alive-prop command.
Note– The number of connections specied by the maximum connections setting is divided
equallyamong the keep-alive threads. If the maximum connections setting is not equally
divisibleby the keep-alive threads setting, the server might allow slightly more than the
maximumnumber of simultaneous keep-alive connections.
Keep-AliveHits
Thekeep-alive hits (number of connections processed) is the number of times a request was
successfullyreceived from a connection that had been kept alive.
Thissetting is not tunable.
Keep-AliveFlushes
Thenumber of times the server had to close a connection because the total number of
connectionsadded exceeded the keep-alive maximum connections setting. The server does not
closeexisting connections when the keep-alive count exceeds the maximum connection size.
Instead,new keep-alive connections are refused and the number of connections refused count
isincremented.
Keep-AliveRefusals
Thenumber of times the server could not hand o the connection to a keep-alive thread,
possiblydue to too many persistent connections (or when total number of connections added
exceedsthe keep-alive maximum connections setting). The suggested tuning is to increase the
keep-alivemaximum connections.
Keep-AliveTimeouts
Thenumber of times the server closed idle keep-alive connections as the client connections
timedout without any activity. This statistic is useful to monitor; no specic tuning is advised.
Keep-AliveTimeout
Thetime (in seconds) before idle keep-alive connections are closed. Set this value in the Admin
Consolein the Timeout eld on the conguration's Performance tab ⇒HTTP tab, under Keep
AliveSettings. The default is 30 seconds, meaning the connection times out if idle for more than
30seconds. The maximum is 3600 seconds (60 minutes). In the command-line interface, use
thetimeout property in the wadm set-keep-alive-prop command.
UsingMonitoringData to TuneYour Server
Chapter2 • Tuning Sun Java System Web Server 55