This section describes the principles of persistent connection operation and time monitoring functionality required to manage the operational conditions of server process (server thread for Windows Version).
In persistent connection (KeepAlive) functionality, the TCP connection does not disconnect even after responding to client request, and waits for the next request from the same client.
You can use this functionality by setting the KeepAlive directive to On, and when the client is responding. When the client sends multiple requests continuously, the response time can be reduced, since the TCP connection is not disconnected.
When waiting for the next request, the server processes are occupied in the client, but you can set the waiting time with the KeepAliveTimeout directive. In the MaxKeepAliveRequests directive, specify how many times a singe client can process the requests with a persistent connection.
You can monitor the time based on the value set in the Timeout directive in the following cases:
If you monitor the process of the ID that is output to the file specified in the PidFile directive, you can monitor Cosminexus HTTP Server control process. The process name (execution program name) to be monitored is httpsd.exe in the Windows version, and httpsd in the UNIX version.
When you monitor the control process, always confirm that the process of the ID stored in the file specified with PidFile directive is Cosminexus HTTP Server process. To confirm that the process is a Cosminexus HTTP Server process, make sure that the execution program name of the process is httpsd.exe in Windows version, and httpsd in UNIX version.