Skip to main content

Why is osfind showing "Out of Memory" error and the osagent is using very high CPU?

  • February 16, 2013
  • 0 replies
  • 0 views

Problem:

  • Product Version: VBE 5.2.1 Full
  • Platform Version: ALL
  • JDK Version: NA
  • Compiler Version: NA
  • Product Component: Osfind

Why is osfind showing "out of memory" error and the osagent is using very high cpu?

Resolution:

This is the expected behavior if a lot of objects are registered with the osagent. To resolve the osfind out of memory problem, the JVM's heap size could be increased while executing osfind, something like:

osfind -J-Xms128m -J-Xmx256m

The above command set the maximum heap size to 256MB and minimum heap size to 128MB. The heap size could be increased as needed.


#VisiBroker
#Security
#heap
#osfind
#osagent
#JVM