cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carles Figuerola (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9375) Cloudstack Management Memory Leak on org.apache.coyote.RequestInfo
Date Fri, 06 May 2016 20:52:12 GMT


Carles Figuerola commented on CLOUDSTACK-9375:

Thanks to everyone for your comments, I've set up three different nodes with different versions.
I still have the node running tomcat6-6.0.24-90.el6.x86_64 which seems to unequivocally be
going to its death ( I set up the second management server
with [~jburwell]'s recommended tomcat6-6.0.43-62.el6 and the third with [~sudhansu]'s recommended
tomcat6-6.0.24-80.el6. I'm also graphing those two servers and we'll see how the test fares.
I'll keep you updated.

Also, [~serverchief], all three hosts seem to have a similar results for the number of threads.
Running that command prints the pid as many times as the number of threads I'm graphing.

> Cloudstack Management Memory Leak on org.apache.coyote.RequestInfo
> ------------------------------------------------------------------
>                 Key: CLOUDSTACK-9375
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.5.2
>         Environment: CentOS release 6.7 (Final)
>            Reporter: Carles Figuerola
> After deploying ACS (cloudstack-management-4.5.2-1.el6.x86_64), using a 4 management
cluster, the management pid keeps crashing with out of memory errors. Eclipse Memory Analyzer
points to this class (org.apache.coyote.RequestInfo) as the culpable one:
> {code}
> 66,923 instances of "org.apache.coyote.RequestInfo", loaded by "org.apache.catalina.loader.StandardClassLoader
@ 0x600026b98" occupy 6,227,824,472 (94.91%) bytes. These instances are referenced from one
instance of "java.lang.Object[]", loaded by "<system class loader>"
> {code}
> Strangely, this is not affecting a smaller installation (2 management,  90 hosts, ~2000
VMs) that is running ACS 4.5.2 over CentOS 6.7 or a clone of the broken one (4 management,
300 hosts, ~4000 VMs) running ACS 4.5.2 over Ubuntu 12.04.

This message was sent by Atlassian JIRA

View raw message