On 07/03/17 22:54, Christopher Schultz wrote:
> All,
> 
> If I stop a Connector (e.g. using JMX), I know that the listen port
> will be unbound and new connections will fail. But what about
> in-process requests?
> 
> My testing shows that with a simple JSP like this:
> 
> <% Thread.sleep(10 * 1000); %>This is a test.
> 
> Stopping the connector during the 10-second interval causes an
> immediate disconnect.
> 
> Pausing the connector allows in-process requests to complete, but then
> won't process any new requests (or even perform a TLS handshake).
> Resuming the connector will process the backlog.
> 
> Is there a particular reason why the stop() operation must terminate
> in-process connections? Is it because (for HTTPS) the SSL engine must
> be destroyed?

No.

It is just in the normal shutdown process the waiting for in-flight
requests happens in the Context so by the time shutdown gets as far as
the Connector it doesn't wait.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to