Does Pega call CG every 10 min?
Hi all,
Just need to understand if Pega call CG very 10 mins? or the JVM kicks in when the mem is low?
Regards
Seri
***Updated by moderator: Lochan to add Categories***
Pegasystems Inc.
AU
But this makes no sense because it is regularly happening every 10 mins.. Plus lots of memory still availble and so JVM should not kick in???
2016-02-23 16:28:21,741 [egaRULES-MasterAgent] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Feb 23 16:28:21 EST 2016 Total memory: 4,187,619,328 Free memory: 393,846,488 Requestor Count: 33 Shared Pages memory usage: 0%
2016-02-23 16:38:21,741 [egaRULES-MasterAgent] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Feb 23 16:38:21 EST 2016 Total memory: 4,187,619,328 Free memory: 718,962,608 Requestor Count: 31 Shared Pages memory usage: 0%
2016-02-23 16:48:21,741 [egaRULES-MasterAgent] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Feb 23 16:48:21 EST 2016 Total memory: 4,187,619,328 Free memory: 810,333,496 Requestor Count: 29 Shared Pages memory usage: 0%
2016-02-23 16:58:21,741 [egaRULES-MasterAgent] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Feb 23 16:58:21 EST 2016 Total memory: 4,187,619,328 Free memory: 1,001,122,720 Requestor Count: 32 Shared Pages memory usage: 0%
Hi Seri,
This is just standard log output and does not indicate that a garbage collection has taken place, though you can see GC is happening by looking at the free memory. You can monitor GC activity by directing your garbage collection output to a logfile.
For Sun JVM use -verbose:gc -Xloggc:/path/to/logs/gcout.log
For IBM JVM use -Xverbosegclog:/path/to/gclog
There are additional arguments for GC logging. See your JVM vendor documentation. You can also monitor GC activity using an external tool like VisualGC.
Pegasystems Inc.
US
Seri,
The logs above is generated by PRPC's Master Agent which wakes up every 10 mins (by default) to log health information about your JVM. To achieve this PRPC system code relies on the underlying Platform MXBeans. These log messages are INFO (informational) and causes no overhead to the application.