Discussion
TDBFG
CA
Last activity: 30 Nov 2016 10:50 EST
Leaking suspects
Not sure why our JAVAcore heap memory is exhausting.
Following are the comments from our consultant.
Please advise.
The javacore files showed that the heapmemory was exhausted:
Free Java heap size: 4.23 KB
Allocated Java heap size: 1.38 GB
The leaking suspect are:
One instance of "com.pega.pegarules.engine.clipboard.DirectStreamEncoder" loaded by "<system class loader>" occupies 321,422,112 (21.76%) bytes.
The memory is accumulated in one instance of "com.pega.pegarules.engine.clipboard.DirectStreamEncoder" loaded by "<system class loader>".
One instance of "com.pega.pegarules.util.collections.StringPoolSet" loaded by "<system class loader>" occupies 227,176,528 (15.38%) bytes.
The memory is accumulated in one instance of "com.pega.pegarules.util.collections.StringPoolSet$Entry[][]" loaded by "<system class loader>".
4,462 instances of "com.pega.pegarules.engine.clipboard.ClipboardPropertyImpl", loaded by "<system class loader>" occupy 611,507,624 (41.40%) bytes.
These instances are referenced from one instance of "java.lang.Object[]", loaded by "<system class loader>"
Please contact your support for the application "com.pega..." for them to further investigate.
***Edited by Moderator: Maryrita , added Group Tag***