Is the size of the https request cause any issues? The IE (hanging on while loading few requests) and Chrome (net::ERR_SSL_PROTOCOL_ERROR) request are working occasionally, what I observed is sometime loads js, css files from cache and then it works fine. If it is trying to download from the server, then it fails to load few https requests out of 47.
I have tried increasing the size of maxHttpHeaderSize=51200, minSpareThreads=200, compression=on, maxConnections=1000 but no luck. Are there anyother tomcat attributes which can back to load the js(maximum size can be around 60 kb), css(maximum size can be around 40 kb) file without any interruptions? -----Original Message----- From: Venkata Reddy P Sent: Sunday, June 05, 2016 11:15 PM To: Tomcat Users List Subject: RE: TLSv1.2 ALERT: fatal, description = unexpected_message Thanks Mark for the reply. I have forgot to mention. My current ssl errors are getting only for IE and google chrome browsers. The same application is working well for the Firefox that's the reason can't suspect the SSL implementation. I have aslo tried with openssl client and confirms the nothing wrong with ssl implementation. The same ssl implantation have been using from tomcat4 onwards and the same implementation has been injected as per the tomcat8 connectors. -----Original Message----- From: Mark Thomas [mailto:ma...@apache.org] Sent: 05 June 2016 22:23 To: Tomcat Users List Subject: Re: TLSv1.2 ALERT: fatal, description = unexpected_message On 05/06/2016 16:32, Venkata Reddy P wrote: > Hi, > > I have a setup with Tomcat8.0.33,jre8u91 and with ssl enabled with http > connector. > <Connector SSLEnabled="true" acceptCount="100" > address="10.4.20.46" connectionTimeout="-1" > disableUploadTimeout="true" enableLookups="false" > maxHttpHeaderSize="8192" > maxThreads="500" port="50002" > protocol="com.poc.tomcat8.SSLHttp11Protocol" > scheme="https" secure="true" /> > > Most of the application works on ssl without any issues but while downloading > JS,CSS files seems to be failing. I can't suspect the ssl implementation. Why not? We haven't seen any reports from users using the default TLS implementation. You are using a custom TLS implementation any you are seeing errors. Absent some VERY strong evidence this is a Tomcat bug, all the indications are that the bug is in com.poc.tomcat8.SSLHttp11Protocol Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
