/var/lib/vco/app-server/bin/java_pid5483.hprof is almost 2GB. This has been haunting me as it destroys my appliance filling it up %100. I have a VM snapshot to revert the appliance when this happens.
-Stephen
usualy this file is generated if there is server crash for example out of memory.
VMware KB: What is the pidXXXXXX.hprof file used for?
In vCO generation of this file can be disabled by removing -XX:+HeapDumpOnOutOfMemoryError from JVM options
In vCO context this option is set in
var/lib/vco/app-server/bin/setenv.sh For vCO Configurator
var/lib/vco/configuration/bin/setenv.sh For vCO Server
After removing it from start-up script services must be restarted.
If the option is sucessfully removed can be validating by checking the running processes list parameters
> ps -fax | grep 'HeapDumpOnOutOfMemoryError'
usualy this file is generated if there is server crash for example out of memory.
VMware KB: What is the pidXXXXXX.hprof file used for?
In vCO generation of this file can be disabled by removing -XX:+HeapDumpOnOutOfMemoryError from JVM options
In vCO context this option is set in
var/lib/vco/app-server/bin/setenv.sh For vCO Configurator
var/lib/vco/configuration/bin/setenv.sh For vCO Server
After removing it from start-up script services must be restarted.
If the option is sucessfully removed can be validating by checking the running processes list parameters
> ps -fax | grep 'HeapDumpOnOutOfMemoryError'
Hi,
I know this is an old post - But a few mintues ago it helped me to figure out what went wrong with our vRO-Appliances the last days!
So just f.y.i. - This problem still occurs on vRO 7.0.1 Appliances!
Thx & Regards,
Marc