Hi Keerati, TomEE SSL layer is 100% Tomcat one so if the issue is linked to SSL it means you need to check Tomcat setup (I'd start by the Connector configuration then probably depending the protocol - apr, https - by the libraries on the machine since Tomcat can be linked to openssl depending how you run it).
That said having a thread dump when it happens (jstack or kill -3 of the process id) would help a lot to validate this hypothesis. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-12-20 12:46 GMT+01:00 Keerati Jittrawong <[email protected]>: > Dear TomEE team, > > > First of all, thanks for making TomEE, and making EJB accessible to all! > We are greatly appreciate your effort. > > > We've been using TomEE for our project for a while, and would like to give > some feedbacks. > > > Previously, we use TomEE 1.7.4 and found a minor bug about cache header > when TomEE serve javascript files (the javascript files does not get cached > by the browser), it seems that there is a bug on cache-related http headers > (the cache header always get overridden by TomEE, so we cannot tell browser > to cache the javascript files). > > > Then, we change to TomEE 7.0.2 and the cache header bug has been resolved. > However, we think we found a bug on SSL feature. We've setup SSL on two > different machine (Redhat and CentOS) using two different SSL certificates, > and the exact same problem happen. > > > At first, TomEE runs normally, but after a few days (we are not exactly > sure how long), TomEE starts to have stability problem. In our case, TomEE > starts to consume CPU usage (~20% on all CPU cores) even when there is no > connection. Furthermore, when users start to really use our server (250 > users, about 1 day), TomEE did crash. So, we decided to disable SSL from > our TomEE server, and everything come back to normal. > > > Sorry that we did not record all the problems appropriately (the time we > test SSL on the 1st and 2nd server is about 2 months), but now that we > found the same problem happen on the 2nd server. We are quite sure that > TomEE has stability problem with SSL. > > > If you want more details or want us to help in anyway, please let us know. > > > Thank you and best regards, > > Keerati >
