4.15.3 Note
- Organization of this subsection
(1) Numbers of server processes and threads
Starting the Web server requires resources according to the number of server processes and the number of threads. If excessively large values are specified, the Web server might not be able to start due to insufficient resources.
(2) How to stop the Web server
In WebSocket communication, request processing does not end until the client or backend server closes the connection. Therefore, even if a planned termination is requested, the Web server cannot terminate until the WebSocket communication terminates. You can stop the Web server by using the following methods:
-
Use the timeout specified in the HWSGracefulStopTimeout directive to trigger the planned termination after the specified time has elapsed.
-
After a planned termination is requested, forcibly stop the Web server by using the normal stop procedure.
-
Stop the Web server by using the normal stop procedure. In this case, the Web server will terminate after the specified number of seconds to wait for termination of server processes (the waiting time varies depending on the platform and settings).
(3) Protocol to be specified in the ProxyPass directive
When forwarding WebSocket communication, specify the forwarding destination URL in the ProxyPass directive by using the format containing ws://host-name[:port-number]/. You cannot specify wss for the protocol of the forwarding destination URL.