Mladen,
On 12/16/20 04:10, Mladen Adamović wrote:
We have experienced a large number of HTTP requests with the problem "No
data received".
this is the example using curl:
--2020-12-15 15:38:13--
https://www.numbeo.com/admin/DownloadLastDbBackupServlet?numbeoPass=xxx
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving www.numbeo.com (www.numbeo.com)... 209.126.119.66
Connecting to www.numbeo.com (www.numbeo.com)|209.126.119.66|:443...
connected.
HTTP request sent, awaiting response... No data received.
Retrying.
--2020-12-15 15:38:15-- (try: 2)
https://www.numbeo.com/admin/DownloadLastDbBackupServlet?numbeoPass=xxx
Connecting to www.numbeo.com (www.numbeo.com)|209.126.119.66|:443...
connected.
HTTP request sent, awaiting response... No data received.
Retrying.
We have a self-monitoring script which runs on server and when the server
is not working properly it does a log save and the service restart.
How do you detect this state? Just make a request and if you get "No
data received" from curl, you restart the server?
We are using currently Apache 8.5.5 and the Connector is set-up as follows
(using Tomcat native):
<Connector port="8181"
protocol="org.apache.coyote.http11.Http11AprProtocol"
SSLCertificateFile="/etc/letsencrypt/live/numbeo.com/cert.pem"
SSLCertificateKeyFile="/etc/letsencrypt/live/
numbeo.com/privkey.pem"
SSLCertificateChainFile="/etc/letsencrypt/live/
numbeo.com/chain.pem"
SSLVerifyClient="optional" SSLProtocol="TLSv1+TLSv1.1+TLSv1.2"
connectionTimeout="20000" acceptCount="30000"
acceptorThreadCount="4"
compression="on" maxConnections="50000" maxThreads="500"
compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,image/svg+xml,image/svg,image/png,image/jpeg"
useSendfile="false"
maxHttpHeaderSize="16392" SSLEnabled="true"
enableLookups="false"
scheme="https" secure="true" clientAuth="false"
useBodyEncodingForURI="true"
URIEncoding="UTF-8"
/>
I see you are using Let's Encrypt. How are you managing the rotating of
the keys and certificates?
*What would be the next steps how to identify the problem and perhaps
solve it?*
What have you done so far?
If we should migrate to the new version, should we try first the last
8.5 version or the last 9 Tomcat version?
I think in general you should upgrade to the latest version which makes
sense for you. That's probably 8.5.61 for now, but maybe you should make
a plan to migrate to Tomcat 9.x over the next few months or years.
Our JSTACK when the last problem occurred is as follows:
root@condor1796 ~ # cat jstack.log
> [...]
I don't see anything that sticks out in your thread dump.
Attaching to process ID 27753, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 25.101-b13
Deadlock Detection:
That JVM seems fairly old, too. Consider upgrading to latest Java 8 VM
(or beyond, if appropriate).
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
