You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Keerati (JIRA)" <ji...@apache.org> on 2017/08/01 11:55:00 UTC

[jira] [Comment Edited] (TOMEE-2000) TomEE PLUME 7.0.2 stability problem when using HTTPS on both Redhat and CentOS

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

Keerati edited comment on TOMEE-2000 at 8/1/17 11:54 AM:
---------------------------------------------------------

-


was (Author: jkeerati):
We already found out that some tomee libraries (jar) are in beta version. Those beta jar cause instability. I'm not sure why our server has those beta libraries, it probably came from TomEE PLUME M3 or some early version of TomEE PLUME 7.0.0. Anyway, the latest version of TomEE PLUME don't have those beta libraries. So, the problem is resolved.

> 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
>             Fix For: 7.0.3
>
>         Attachments: CPU usage 20170202.png, %CPU usage (java) with zero request.png, jstack-20170202.out, 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.4.14#64029)