You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Tillmann Schulz <ti...@yahoo.de.INVALID> on 2020/03/12 15:01:43 UTC
Tomcat 8.5.51 (Linux) issue with the tomcat manager and empty
responses of the manager's "stop" command
Hello tomcat user group,
since our update from Tomcat 8.5.50 to 8.5.51 (Linux) I got a issue with the "tomcat manager", when calling the manager's "stop" command by socket command.
With the following socket command I try to stop the application app1:
GET /manager/text/stop?path=/app1 HTTP/1.1
In some cases the response is empty.
Our log says:
2020-03-10 19:17:14,951 [pool-1-thread-1] DEBUG - MANAGER REQUEST: GET /manager/text/stop?path=/app1 HTTP/1.1
Host: localhost:8080
Authorization: Basic xxxxxxxxxxxxxxx
2020-03-10 19:17:34,977 [pool-1-thread-1] DEBUG - MANAGER RESPONSE:
As you see the stop command has no response after a time of 20 seconds (Client Socket Timeout is 5 minutes)
I guess that the tomcat (serverside/servlet) timeout of 20 seconds causes the call to end.
But why is the response in some cases empty? This is not as described in the tomcat documentation.
Is it possible, that the tomcat server is stopped, when the issue occurs? But why is there a delay of 20 secs?
And why does this issue not occur with tomcat 8.5.50?
Thank you for your help
Tillmann Schulz
Re: Tomcat 8.5.51 (Linux) issue with the tomcat manager and empty
responses of the manager's "stop" command
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Tillmann,
On 3/12/20 11:01, Tillmann Schulz wrote:
> Hello tomcat user group,
>
> since our update from Tomcat 8.5.50 to 8.5.51 (Linux) I got a issue
> with the "tomcat manager", when calling the manager's "stop"
> command by socket command. With the following socket command I try
> to stop the application app1: GET /manager/text/stop?path=/app1
> HTTP/1.1
>
>
> In some cases the response is empty. Our log says:
>
> 2020-03-10 19:17:14,951 [pool-1-thread-1] DEBUG - MANAGER REQUEST:
> GET /manager/text/stop?path=/app1 HTTP/1.1 Host: localhost:8080
> Authorization: Basic xxxxxxxxxxxxxxx 2020-03-10 19:17:34,977
> [pool-1-thread-1] DEBUG - MANAGER RESPONSE:
>
>
> As you see the stop command has no response after a time of 20
> seconds (Client Socket Timeout is 5 minutes) I guess that the
> tomcat (serverside/servlet) timeout of 20 seconds causes the call
> to end.
>
> But why is the response in some cases empty? This is not as
> described in the tomcat documentation.
>
> Is it possible, that the tomcat server is stopped, when the issue
> occurs? But why is there a delay of 20 secs? And why does this
> issue not occur with tomcat 8.5.50?
Are you able to make other /manager requests and get a good response?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl5qivcACgkQHPApP6U8
pFi4qQ/+LYetRFfD+pIs0LAynSO00nkakwcQa8cO9QrmUtYH9GChZL3UiDFerVFi
Ejr+sONASD3iaZ3t3/9JTapZGUV9yL6EIW043X1cnvHqP3Z8vUkQ3VNRjyNIEoH0
Pga2taSC27DORi7+oPWWKBvIib7q9V0AL1BQUo0t4XkapXKD+Mu6+9sS3IlSt8wi
s7b680rK94MyHAx4qW/3NuNOwcZEuOYkNtElOkrTgfJu+SVZyVdN5NpvWWxWUUVR
+MUHHpJjgKk2sUBvjljI1oKlVhAN53Z1EAiZ8E1avauJZS1w9IJW4nCd1FnL6WZf
v8MIKhTUGlJBsarzqLOZKzP4Dg+v1HdFQHqQ9dJd6kD6dxdiI+PKBCL6WwM3oGR+
il2jqVYU4XTH/DFuGd3b5yyVyr/8qAxKxTk1M+kAItCTBCcuEN9QeAXfOI3JAbbc
QZMjpV2UZRyMwIza0v79TtDs0WkEsXkZYRx9+eoJe118RLqObA2aGpj8gcKTnzJK
TlZbqxV4fmlGlnEARsdjisBJaDdjO48j07b5G/kh1l/CmWVtZnfNCxlIFqNNa2p9
gmQPl7xEnsflrLvN4nTj6XiUMRlGa1xz+l4CHZxxkRn4x694hkLl0usZOsWy41f9
5KgVGaOxcREQqWv4jG2IeLUaPWV3j6+HxrPuZPxccg7zHf5TGnQ=
=IuoT
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org