[
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834043#comment-15834043
]
Keerati edited comment on TOMEE-2000 at 1/23/17 8:17 AM:
---------------------------------------------------------
Hi Romain,
We use Oracle JVM (java 1.8).
We also use TomEE to serve static web content. So, we use standalone TomEE (we
didn't use "httpd" Apache HTTP Server at all).
was (Author: jkeerati):
Hi Romain,
We use Oracle JVM (java 1.8).
We use standalone TomEE (we didn't use "httpd" Apache HTTP Server).
> 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
> Attachments: %CPU usage (java) with zero request.png, jstack.out
>
>
> 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)
