[ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831182#comment-15831182
 ] 

Keerati commented on TOMEE-2000:
--------------------------------

1. What sort of workloads is your server handling? Specifically, I'm curious 
about requests per second, and the types of request.
just a simple https GET/POST requests (user session is handling by TomEE). For 
the first case, requests per second is less than 50 . For the 2nd case, 
requests per second is less than 1. I think the problem comes from time than 
requests per second. It takes a few days for the problem to develop.

2. How do you have SSL configured - have you just imported your private key / 
certificate to a java keystore, or do you use the native connector?
I import my private key / certificate to a java keystore.

3. Are you using BIO or NIO on your HTTPS connector (you could provide 
server.xml with any sensitive data removed)
We uses HTTP/1.1 auto-switching mechanism. Below is a sample of our server.xml.

    <Connector port="443" protocol="HTTP/1.1"
               maxThreads="500" SSLEnabled="true" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS"
               keystoreFile="xxx"
               keystorePass="xxx" keyAlias="xxx"
        ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_1$
   TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS$
   TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AE$
   TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA"/>

4. Probably the most helpful thing would be to get a thread dump when your 
server is in this state. To do that, you can run jstack passing the PID of 
TomEE in as a parameter. If you're able to get that and send it to the mailing 
list or attach it to this ticket, that would be really helpful.
If we success in reproducing the problem, we will send you the thread dump.

> TomEE PLUME 7.0.2 stability problem when using HTTPS on both Redhat and CentOS
> ------------------------------------------------------------------------------
>
>                 Key: TOMEE-2000
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2000
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.2
>         Environment: Red Hat Enterprise Linux Server release 7.2 (Maipo)
> CentOS Linux release 7.2.1511 (Core) 
> Java(TM) SE Runtime Environment (build 1.8.0_101-b13) (64-bit server)
>            Reporter: Keerati
>
> There seems to be a bug on HTTPS 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 have abnormal CPU consumption (~20% on all CPU cores) even when there is 
> no connection. Furthermore, when the server start to have HTTPS workloads, 
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to