![[Contents]](FIGURE/CONTENT.GIF)
uCosminexus Application Server, HTTP Server User Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Display number of running processes, number of standby processes, and the status of each process (such as R, W, and L) in the Web browser (number of server threads for Windows version). On the basis of this information, you can tune the StartServers, MinSpareServers, MaxSpareServers, and the MaxClients directive (the ThreadsPerChild directive for Windows version). For details on each directive, see 4.1 Relationship between processes and directives of Cosminexus HTTP Server.
When you set the ExtendedStatus directive to On, more detailed information is displayed.
Specify the server-status handler as follows to use the display functionality of status information:
<Location /server-status>
SetHandler server-status
</Location>
|
However, generally the access to the status information of the Web server is controlled and the information is not disclosed to the end-user.
To display the status information, specify the URL from Web browser in the following format. Note that the server status may be displayed incorrect temporarily depending upon the timings:
http://Host-name[:Port-number]/server-status[?{refresh=Update interval|auto|notable}]
|
You can specify refresh=updated interval, auto, and notable respectively with the conjunction &. However, the auto is in the plain text, and hence there is no significance of specifying auto together with notable.
http://www.example.com/server-status?refresh=60¬able
http://www.example.com/server-status
Figure 4-11 Example of status information display
![[Figure]](FIGURE/ZU021100.GIF)
The following table describes the information that you can acquire by the status information display functionality. You can acquire the detailed information by setting the ExtendedStatus directive to On.
Table 4-13 Information which can be acquired by using the status information display functionality (without the auto specification)
| No. | Contents | Explanation | Value and acquisition of ExtendedStatus | |
|---|---|---|---|---|
| Off | On | |||
| 1 | Server Version | Server version | Y | Y |
| 2 | Server Built | Server building time | Y | Y |
| 3 | Current Time | Current time | Y | Y |
| 4 | Restart Time | Start time | Y | Y |
| 5 | Parent Server Generation | Number of times the server process is restarted (initial value 0) | Y | Y |
| 6 | Server uptime | Server process running time | Y | Y |
| 7 | Total accesses | Number of total accesses | N | Y |
| 8 | Total Traffic | Total amount of traffic | N | Y |
| 9 | CPU Usage: u vvv s www cu xxx cs yyy - zzz% CPU load | User time, system time, user time of the child process, system time of the child process, CPU usage rate (UNIX version) | N | Y |
| 10 | xxx requests/sec - yyy B/second - zzz B/request | Number of requests per second, traffic per second, traffic per request | N | Y |
| 11 | xxx requests currently being processed, yyy idle workers | The number of server processes during request processing (threads), the number of server processes in the status of request waiting (threads) | Y | Y |
| 12 | Scoreboard | Operation status of a single thread | Y | Y |
| 13 | Scoreboard Key | Legend of scoreboard | Y | Y |
| 14 | PID Key | Server process ID and the operation status of a single thread | Y | Y |
| 15 | Srv | Identifiers and restart frequency of server process | N | Y |
| 16 | PID | Process ID | N | Y |
| 17 | Acc | Access count (connection-wise/ thread-wise/ slot-wise) | N | Y |
| 18 | M | Operation status | N | Y |
| 19 | CPU | CPU time (in seconds) (UNIX version) | N | Y |
| 20 | SS | Elapsed seconds from the starting of last process | N | Y |
| 21 | Req | Milliseconds required for the last process | N | Y |
| 22 | Conn | Traffic for the connection | N | Y |
| 23 | Child | Traffic of process | N | Y |
| 24 | Slot | Traffic of slot | N | Y |
| 25 | Client | Client of last process | N | Y |
| 26 | VHost | Virtual host name | N | Y |
| 27 | Request | Request line of last process | N | Y |
Table 4-14 Information which can be acquired by using the status information display functionality (with the auto specification)
| No | Contents | Explanation | Value and acquisition of ExtendedStatus | |
|---|---|---|---|---|
| Off | On | |||
| 1 | Total accesses | Total number of accesses | N | Y |
| 2 | Total kBytes | Total amount of traffic | N | Y |
| 3 | CPULoad | CPU usage rate (UNIX version) | N | Y |
| 4 | Uptime | Server process running time (in seconds) | N | Y |
| 5 | ReqPerSec | The number of requests per second | N | Y |
| 6 | BytesPerSec | Amount of traffic per second | N | Y |
| 7 | BytesPerReq | Amount of traffic per request | N | Y |
| 8 | BusyWorkers | The number of server processes during request processing (threads) | Y | Y |
| 9 | IdleWorkers | The number of server processes in the status of request waiting (threads) | Y | Y |
| 10 | Scoreboard | Operation status of each thread | Y | Y |
Multibyte characters might be set in the information for the time zones of Current Time and Restart Time displayed by using the server status display functionality. In this case, Cosminexus HTTP Server escapes all of the character strings (replaces them with the character strings configured with the prefixes which start with \x and hexadecimal codes).
All Rights Reserved. Copyright (C) 2012, Hitachi, Ltd.