You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Christopher Schultz <ch...@christopherschultz.net> on 2017/03/07 22:54:15 UTC
Implications of stopping a connector
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJYvzoXAAoJEBzwKT+lPKRYySIP/0zfk1bTv2USpFuuc0LjYAaz
O/RBy9qlZpOqArngDO1cP/AWsa9iMQ2348pgQStmhk2yhuCKHUaqvbOaUEyJBQ8L
RkPWWY1rZ1Q77LnNW2IjeBrJP1YfNgwH23IxHWUImGPtqK+uk5l7qEK64eSZYtq/
ARFIgmPfBBo9UMi6kEq3oIy1nhfmcbJBYoXO3HGJ6nF6or1t5Dgq6bKKAyeOn1Ra
STxUvjiqiHe2DrbJm7l0EGc2+yZt18TPINejdOt8XvjF/AsnMPFZrfYSoHjcHyFL
+qYrYETko97W4k3EtzEjN1xThX/jA/m1ZAvZwE23Iaz/uZE+gQdpHeQ//eWmTN7s
4xCsnhmnYibMzXVkxo6ZG+o9CSLmmhgPyvGGxaoDozAOy90yDHNZRYQ6foIMgDJ/
k6XPMKAJIIR2tiQDWY2Jqmsub3alP9ZH776qzonFZ0j6ZSc//CwubzlVNnbwzHNQ
t5XpH/TUykX5qhpA0GsPIjqHQ2wHrA/m2aI4RuDao4w/ZihcAteoJ8JNE5u+dn3n
wo2t15foYrQ16M2gCjMmU0OTGix0NomUnGr3p2ko9ksCqbNQus1YGtBua5tplew+
0eXBwYHpwci5F+2+p8VQesh4SUvjyrqxqAlHEO3HO4V5dBC1qzfjcQ5WS8KcRDe9
7gcQNZLQPcijJbku+JK5
=b4VO
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Implications of stopping a connector
Posted by Mark Thomas <ma...@apache.org>.
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org