java.lang.OutOfMemoryError: Java heap space

[FSvcoe]

Have continued to receive the message above-What would be the best value to set? The wrapper.conf values below:

# Java Classpath (include wrapper.jar)  Add class path elements as

#  needed starting from 1

wrapper.java.classpath.1=.

wrapper.java.classpath.2=./wrapper.jar

wrapper.java.classpath.3=./run.jar

wrapper.java.classpath.4=./o11n-jbossmain.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)

wrapper.java.library.path.1=.

# Java Additional Parameters

wrapper.java.additional.1=-XX:PermSize=256m

wrapper.java.additional.2=-XX:MaxPermSize=256m

wrapper.java.additional.3=-Xmn768m

wrapper.java.additional.4=-XX:+CMSClassUnloadingEnabled

wrapper.java.additional.5=-Xss256k

wrapper.java.additional.6=-XX:SurvivorRatio=8

wrapper.java.additional.7=-XX:TargetSurvivorRatio=90

wrapper.java.additional.8=-Dsun.rmi.dgc.client.gcInterval=3600000

wrapper.java.additional.9=-Dsun.rmi.dgc.server.gcInterval=3600000

# Initial Java Heap Size (in MB)

wrapper.java.initmemory=2048

# Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=2048

# Application parameters.  Add parameters as needed starting from 1

# wrapper.app.parameter.1=

# wrapper.app.parameter.2=

# wrapper.app.parameter.3=

# Port which the native wrapper code will attempt to connect to

wrapper.port=1777

#********************************************************************

# Wrapper Logging Properties

#********************************************************************

# Format of output for the console.  (See docs for formats)

wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)

wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.

wrapper.logfile=./wrapper.log

# Format of output for the log file.  (See docs for formats)

wrapper.logfile.format=LPTM

# Log Level for log file output.  (See docs for log levels)

wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before

#  the log is rolled. Size is specified in bytes.  The default value

#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or

#  'm' (mb) suffix.  For example: 10m = 10 megabytes.

wrapper.logfile.maxsize=2m

# Maximum number of rolled log files which will be allowed before old

#  files are deleted.  The default value of 0 implies no limit.

wrapper.logfile.maxfiles=5

# Log Level for sys/event log output.  (See docs for log levels)

wrapper.syslog.loglevel=NONE

#********************************************************************

# Wrapper NT Service Properties

#********************************************************************

# WARNING - Do not modify any of these properties when an application

#  using this configuration file has been installed as a service.

#  Please uninstall the service before modifying this section.  The

#  service can then be reinstalled.

# Name of the service

wrapper.ntservice.name=VMwareOrchestrator

# Display name of the service

wrapper.ntservice.displayname=VMware vCenter Orchestrator Server

# Description of the service

wrapper.ntservice.description=Hosts the VMware vCenter Orchestrator Server. If the service is running, you cannot start another server in command line.

# Service dependencies.  Add dependencies as needed starting from 1

wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START or DEMAND_START

wrapper.ntservice.starttype=AUTO_START

# Priority at which the service is run.  NORMAL, LOW, HIGH, or

#  REALTIME

wrapper.ntservice.process_priority=NORMAL

# Allow the service to interact with the desktop.

wrapper.ntservice.interactive=true

# Set the wrapper timeout in seconds. 0=no timeout.

wrapper.ping.timeout=0

[cdecanini_ · Accepted solution]

Before changing the default configuration it would be a good think to check why you are hitting the 2 GB.

• What are the plug-ins that are loaded ?
• If vCenter plug-in : how many VMs approximately ?
• Are you doing intense operations / workflows in parallel ?

I ask this because it is very rare customers are hitting the default limit and in most cases when it hapened customers had some custom plug-ins using memory and not returning it.

Also please refer to this article

This could help you to determine the behavior of the memory consumption (peak during specific operation or regular growth ...).

Christophe.

[FSvcoe]

Thanks for the reply Christophe. The VC has approx. 1375 VM's running.Here's a screenshot of the current plugin stack, and the error message trying to access the VUM plugin. I've downloaded the utility you suggested, and will see what it tells us. Thanks.

[cdecanini_]

The amount of VM you have is definitely not the problem.

What I suggest at this point is to :

• Restart your vCO server, check the server.log file for errors.
• Monitor the RAM usage. Check behavior with server not running workflows over time and then operationg your regular workflows.
• Disable all plug-ins in the configuration page. Enable one, start the server, use the workflows that you operate frequently that apply to this plug-in - check memory usage, restart operation until you find the one consuming all the memory.

And to ping GSS on your VUM plug-in issue.

Christophe.

[FSvcoe]

Christophe,

Thanks for the link on tracking memory usage. For anyone else that might be interested, it will write the heap values every 10 seconds to the server.log file (example below). Very helpful for seeing usage.

2011-10-07 10:42:19.482-0400 INFO  [MEMORY_DUMP] 520.803 MB / 1.926 GB

2011-10-07 10:42:29.482-0400 INFO  [MEMORY_DUMP] 523.057 MB / 1.926 GB

2011-10-07 10:42:39.483-0400 INFO  [MEMORY_DUMP] 525.247 MB / 1.926 GB

I did do a fresh install and then add the plugins in separately, starting with VUM and then VIX. Both were consuming approx. 250 MB of memory.

I was able to address the VUM plugin failing by creating a backup of my VCO config, removing and reinstalling Orchestrator, and then adding the VUM plugin first, with the VIX plugin second. I don't know why the order would make a difference but it did fix the issue