Discussion

1
Replies
101
Views
MansimranB Member since 2016 4 posts
TDBFG
Posted: 4 years ago
Last activity: 4 years 4 months ago
Closed

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: Maryritaadded Group Tag***
 

Moderation Team has archived post
Share this page LinkedIn