How to identify which process ran out of memory and created the HPROF file

Products

• Service Virtualization
• CA Application Test

Issue/Introduction

There are times multiple DevTest components like Registry, Identity Access Manager Service, Portal, Simulator, Dashboard, Coordinator, Broke are running on the same server and a java_pidxxxx.hprof file is created in DevTest_Home/tmp folder. Not sure which component of the DevTest ran out of memory and need to be configured with more memory in ".vmoptions" file.

The below screenshot shows the HPROF file in DevTest/tmp folder.

 

Environment

Release : 10.0

Cause

One of the component ran out of memory.

Resolution

From the HPROF file the process id (pid) refers to the specific component. In the java_pid7080.hprof, 7080 is the process id of the component ran out of memory. You can find the process id in the Task Manager and see which component it is and increase the memory in specific VMOPTIONS file.

Additional Information

Memory Settings