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

2017-08-01 Thread Keerati (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


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

2017-08-01 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


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
> 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)


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

2017-02-06 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


sorry for late reply. I guess your suggestion is correct. If we have time, we 
will test this issue on tomcat 8.5.6. 

> 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 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.3.15#6346)


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

2017-02-02 Thread Keerati (JIRA)

 [ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keerati updated TOMEE-2000:
---
Attachment: CPU usage 20170202.png

> 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 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.3.15#6346)


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

2017-02-02 Thread Keerati (JIRA)

 [ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keerati updated TOMEE-2000:
---
Attachment: jstack-20170202.out

> 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 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.3.15#6346)


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

2017-02-02 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


After connecting web app to database and wait a few days, the problem 
reoccurred. So, it seems that the problem is related to database (we're using 
postgres 9.4), but it is strange that the problem occurs only when we use HTTPS 
(plain HTTP with db connection does not cause the problem).

We already make the thread dump and a screenshot. Please let us know, if you 
want more information.

> 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.15#6346)


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

2017-01-30 Thread Keerati (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keerati commented on  TOMEE-2000 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TomEE PLUME 7.0.2 stability problem when using HTTPS on both Redhat and CentOS  
 
 
 
 
 
 
 
 
 
 
We dropped AJP connector wait for 3-4 days, and the problem did not occur again. But during that time, our web app have problem connecting with database. So, we are not sure the problem is solved from dropping AJP or from not connecting database. Now, we are testing again with database connection and without AJP. We will inform you again for the result. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   



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

2017-01-23 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


You mean that from my thread dump there is a blocking call on IO, and it seems 
to cause from JVM?

> 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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati edited comment on TOMEE-2000 at 1/23/17 8:35 AM:
-

We just install OpenJDK to use jstack, we will recheck which jvm TomEE is 
running.

Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the problem still persist? It will require a few more days to 
validate the result.



We should comment out the above line, is that correct?



was (Author: jkeerati):
We just install OpenJDK to use jstack, we will recheck which jvm TomEE is 
running.

Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the above line, is that correct?


> 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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati edited comment on TOMEE-2000 at 1/23/17 8:34 AM:
-

We just install OpenJDK to use jstack, we will recheck which jvm TomEE is 
running.

Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the above line, is that correct?



was (Author: jkeerati):
We just install OpenJDK to use jstack, we will recheck which jvm TomEE is 
running.

Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the following line, is that correct?


> 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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati edited comment on TOMEE-2000 at 1/23/17 8:32 AM:
-

We just install OpenJDK to use jstack, we will recheck which jvm TomEE is 
running.

Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the following line, is that correct?



was (Author: jkeerati):
We just install OpenJDK to use jstack, but TomEE is running on Oracle JVM.
Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the following line, is that correct?


> 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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


We just install OpenJDK to use jstack, but TomEE is running on Oracle JVM.
Do you mean that we should drop the AJP connector, restart the server, and 
let's see whether the server still persist? It will require a few more days to 
validate the result.



We should comment out the following line, is that correct?


> 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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati edited comment on TOMEE-2000 at 1/23/17 8:20 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).


was (Author: jkeerati):
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).

> 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)


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

2017-01-23 Thread Keerati (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


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

2017-01-23 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


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)


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

2017-01-22 Thread Keerati (JIRA)

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

Keerati edited comment on TOMEE-2000 at 1/23/17 6:51 AM:
-

This time we setup HTTPS, with very little server load (just a few page refresh 
I do manually). The first day, everything is working normally. Then, I come to 
check the server again today (today is the 4th day that the server is running), 
and the problem already occurred. So, I capture the cpu usage, and make the 
thread dump.

If there are other things we can help please let us know :)


was (Author: jkeerati):
This time we setup HTTPS, with very little server load (just a few page refresh 
I do manually). The first day, everything is working normally. Then, I come to 
check the server again today (today is the 4th day that the server is running), 
and the problem already occur. So, I capture the cpu usage, and make the thread 
dump.

If there is other things we can help please let us know :)

> 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)


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

2017-01-22 Thread Keerati (JIRA)

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

Keerati commented on TOMEE-2000:


This time we setup HTTPS, with very little server load (just a few page refresh 
I do manually). The first day, everything is working normally. Then, I come to 
check the server again today (today is the 4th day that the server is running), 
and the problem already occur. So, I capture the cpu usage, and make the thread 
dump.

If there is other things we can help please let us know :)

> 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)


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

2017-01-22 Thread Keerati (JIRA)

 [ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keerati updated TOMEE-2000:
---
Attachment: jstack.out

Thread dump when the problem occur.

> 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)


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

2017-01-22 Thread Keerati (JIRA)

 [ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keerati updated TOMEE-2000:
---
Attachment: %CPU usage (java) with zero request.png

> 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
>
>
> 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)


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

2017-01-19 Thread Keerati (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMEE-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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.



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)