-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Suvendu,
Which version of Tomcat? On 1/17/18 8:20 AM, Suvendu Sekhar Mondal wrote: > I am seeing one issue. Under high load sporadically one web > service call fails with: "java.net.SocketTimeoutException: Read > timed out" after 60 Sec mark. > > In our app, httpd routes requests to 8888 then it get redirected > to 8889. Can you be very explicit about what you mean by "redirect", here? > Connector which listens on 8888 has connectionTimeout=20000 but the > one which listens to 8889 does not have any connectionTimeout set > explicitly. As per doc, default connectionTimeout value 60 Sec will > be set for connector which listens on 8889 - and that is playing a > role here. Do you think this assumption is correct? > > Here are the connector properties: <Connector port="8888" > protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8889" > /> So you are probably expecting that all HTTP traffic to :8888 will be redirected to HTTPS over :8889? How long does the redirect take? Under heavy load, you might be running out of threads depending upon a lot of factors, such as what kind of protocol and endpoint are actually being used. It looks like you are using the APR connector (due to SSLCertificateFile) which has some positive attributes with request to scalability while NIO would probably be the best choice if possible. It's got terrible performance, though, unless you use the OpenSSL provider (which requires Tomcat 8.5 or later). > <Connector port="8889" SSLCertificateFile="C:/mycer.cer" > SSLCertificateKeyFile="C:\mykey.key" SSLEnabled="true" > acceptCount="100" clientAuth="false" disableUploadTimeout="true" > enableLookups="false" keystoreFile="conf/.keystore" > maxHttpHeaderSize="8192" maxSavePostSize="-1" maxThreads="200" > minSpareThreads="20" protocol="HTTP/1.1" scheme="https" > secure="true" sslProtocol="TLS1.2" > compressableMimeTypes="text/html,text/xml,text/plain,application/json" > > compressionMinSize="2048" > compression="force" threadPriority="6" /> When you say "high load", what kind of load are you talking about, specifically? You may simply have too much traffic for your existing hardware to handle. No amount of configuration can fix that. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlpfg7sdHGNocmlzQGNo cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFj12Q//WlJMd0JpQJVqFt1z d3aI52pVFQih3Bii8UOAZzZr6omPqqFlkKt2cnAg8lWA3KQaQLJRyzlJKthIzNsB 12nMQlbQzCJZqn1IzggxtEWNL8KDVFY3fo2heJLrEANrIcXx+C6MAb1FLTeZ2/XP V9R1u5q8mOdVgPyj4vITIsjn0oaa4pZ/ypkYwRATT9BRBy8rxkzVneDKPo8ILfdZ Cp1Says1JD4uIEJn9VUlITOC1/08XyeHtrZXR3j3w9A07x9mLdHjVi6yxyyGcMoz u0X/bt1E+Q6LkfTaQ64ubh2dbPXW4JgQy8I43Qzbxytwc2SdB691Un8lAhdnxaIk zBioeiR4Kp+ATOuwbSPqJZ8n15pJENp95KvtR7B+xKn2klKMhuXHMb98OwdL7XBu AeoGW1+RNpEwq1A8l4XmrmvFmrkqKTJVM8kxrPM3lTpTuQcvEtKk0OHOqlD10TGm ldxP61qBLPK1ekjF/8CWxCO011wIvCoWySI8FDLOeXAo8F0ueBA0okajB2+9usqK KpMckGQuRsoC6yVKMAz+ej3UCMiqQPSuuK06Pv8UrI7qTRGqRkBtVcSOIucXKC0S 6QrB4Mm6HajD7+d2/bOd4lJGRSSx3IoWNRx62Hthu9H2MTpp1/EWTwc5aesq2Zmo OVsym/pIs8akxDw3Fkux5Imwr40= =DLo7 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
