]
Michal Karm Babacek commented on MODCLUSTER-522:
------------------------------------------------
Gonna try setting {{status-interval}} attribute of the mod_cluster subsystem element in
Wildfly and setting {{org.jboss.modcluster.container.catalina.status-frequency}} for
Tomcat to something higher than 1 (means 10 seconds). If it helps, it's {{STATUS}}
message; if it doesn't it's probably {{CONFIG}} or {{*-APP}} logic.
Memory leak in processing MCMP, wrong apr pool used for allocation
------------------------------------------------------------------
Key: MODCLUSTER-522
URL:
https://issues.jboss.org/browse/MODCLUSTER-522
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.3.1.Final, 2.0.0.Alpha1
Environment: Solaris 10 x86_64, RHEL 6, Fedora 24, httpd 2.4.6, httpd 2.4.20
Reporter: Michal Karm Babacek
Assignee: Michal Karm Babacek
Priority: Critical
Attachments: mod_cluster-mem.jpg, mod_cluster-mem1.jpg
There seems to be a wrong apr pool used for processing certain MCMP commands. We should
use short life span pools for immediate processing and server-lifetime pools only for
really persistent configuration. In the current state, with 20+ tomcat workers (1 alias
and 1 context each) and virtually no client requests, we could see slow, but steady growth
of heap allocated memory.
TODO: Investigate the offending logic, make sure we ain't using long-lived pools for
immediate processing.
Originally discovered by: [~j_sykora] and [~jmsantuci]
Illustrative memory overview - with constant number of Tomcats: