[
https://issues.apache.org/jira/browse/CLOUDSTACK-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271146#comment-15271146
]
ilya musayev commented on CLOUDSTACK-9375:
------------------------------------------
please share the output of "ulimit -a" from cloud user
Also, please setup a cronjob that would sample number of cloudstack threads on
the host that crashes.. here is an example of a script you can put in cronjob
- for cloud user, I'd set it to run every minute..
#!/bin/bash
CLOUDSTACKPID=$(jps | grep Boot | awk '{print $1}')
date | tee -a counter.$CLOUDSTACKPID
ps -L -o pid= -p$CLOUDSTACKPID | wc -l | tee -a counter.$CLOUDSTACKPID
> Cloudstack Management Memory Leak on org.apache.coyote.RequestInfo
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-9375
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9375
> 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
(v6.3.4#6332)
