Sounds like it might be a GC issue. You can run 'jstat -gc <PID> 1s' to get a view of the memory. OC is 'Old Gen Configured' (your max heap) and 'OU' is Old Gen currently in use. If OU is close to OC, over time, and the FGC column (Full GC count) increasing steadily then the CPU is definitely being spent on GC.
You'll want to do a heap dump to see what's holding the memory - 'jmap -histo:live <PID>' to get a nice histogram of the current heap or 'jmap -dump:live,format=b,file=<dump-file-name>' to dump the actual heap for actual object inspection. --Jens On Wed, Dec 2, 2015 at 9:51 AM, Catanzarite, P. (Paul) < [email protected]> wrote: > We have a gemfire client/server cluster that we’ve noticed our locator is > running a sustained 50 – 100% cpu utilization. We stopped all work in this > environment (test) and the cpu has remained the same. We are running > gemfire v8.1, java 1.7 on linux VM RHEL 6. Any suggestions on what to look > at to see what may be causing this? > > Thanks. > > -Paul > > > --------------------------------------------------------- > > NOTICE: The information contained in this electronic mail message is > confidential and intended only for certain recipients. If you are not an > intended recipient, you are hereby notified that any disclosure, > reproduction, distribution or other use of this communication and any > attachments is strictly prohibited. If you have received this > communication in error, please notify the sender by reply transmission and > delete the message without copying or disclosing it. > > > ============================================================================================ >
