Search the VMware Knowledge Base (KB)
View by Article ID

"Timeout, unable to get property name" in vRealize Orchestrator (2007423)

  • 2 Ratings

Symptoms

    • vRealize Orchestrator (formerly known as vCenter Orchestrator) times out when managing large vCenter Server inventories.
    • vRealize Orchestrator times out when running a Workflow that selects a Host object as an input parameter.
    • vRealize Orchestrator experiences performance degradation in large vSphere environment under heavy load.
    • In the vRealize Orchestrator GUI and the server.log file, you see these errors:

      Timeout, unable to get property 'name'
      com.vmware.vmo.plugin.vi4.model.TimeoutException

      ERROR [STDERR] java.lang.OutOfMemoryError: GC overhead limit exceeded
      java.lang.OutOfMemoryError: Java heap space


    • You see this issue using Web Views or when running workflows directly.
    • This issue may occur on other queries that select a Host object as an input parameter.

    Cause

    The issue occurs due to the Java Heap running low or excessive garbage collection.

    For information on debugging Java Heap usage, see Monitoring the vCenter Orchestrator Java Virtual Machine.

    Resolution

    To resolve the issue, increase the maximum heap size.

    In the Windows installation:
    1. Open the Program Files/VMware/Orchestrator/app-server/bin/wrapper.conf file using a text editor.
    2. Depending on the available memory on your vRealize Orchestrator server, adjust the below value appropriately. Ensure that there is enough additional free memory for the operating system and other components.

      To increase heap (in this example it is to 6GB):

      1. Add this line:

        wrapper.java.additional.NN="-Xmx6144m"  , where NN is the next number in the list

      2. Set the value of java maximum memory by modifying the maxmemory line to:

        wrapper.java.maxmemory=0

        Note: maxmemory must be set to 0 to allow Xmx to be used.

        For example, extract of the wrapper.conf file:

        wrapper.java.additional.20="-Djavax.net.ssl.trustStorePassword=dunesdunes"
        wrapper.java.additional.21="-Djsse.enableSNIExtension=false"
        wrapper.java.additional.22="-Djava.io.tmpdir=%CATALINA_BASE%\temp"
        wrapper.java.maxmemory=4096

        Changes to:

        wrapper.java.additional.20="-Djavax.net.ssl.trustStorePassword=dunesdunes"
        wrapper.java.additional.21="-Djsse.enableSNIExtension=false"
        wrapper.java.additional.22="-Djava.io.tmpdir=%CATALINA_BASE%\temp"
        wrapper.java.additional.23="-Xmx6144m"
        wrapper.java.maxmemory=0

    3. Make the same changes to the Program Files/VMware/Orchestrator/app-server/bin/wrapper-auto.conf file.

    In the vRealize Orchestrator Appliance (formerly known as vCenter Orchestrator Appliance):

    1. Open this file using a text editor:

      vRealize Orchestrator 5.1 - /opt/vmo/app-server/bin/orchestrator.sh.

      vRealize Orchestrator 5.5 and vRealize Orchestrator 6.x - /usr/lib/vco/app-server/bin/setenv.sh.

    2. Modify this line in the file:

      In vRealize Orchestrator 5.1 - MEMORY_SIZE="-Xmx<JVM_Max_Size_in_MB>m -Xmn768m -XX:PermSize=256m -XX:MaxPermSize=256m -Xss256k -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90"

      In vRealize Orchestrator 5.5 and vRealize Orchestrator 6.x - MEM_OPTS="-Xmx2048m -XX:MaxPermSize=256m -Xss256k -XX:+HeapDumpOnOutOfMemoryError"

    3. Depending on the available memory on your vRealize Orchestrator appliance, set the maximum size appropriately.

      For example, for vRealize Orchestrator 5.1:

      MEMORY_SIZE=" -Xmx2048m -Xmn768m -XX:PermSize=256m -XX:MaxPermSize=256m -Xss256k -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90"

    Tags

    vRealize Orchestartor-times-out

    See Also

    Update History

    04/16/2014 - Added the file path for the 5.5.1 version. 03/17/2014 - Added 5.1.x and 5.5.x to Product Versions 03/26/2014 - Added steps to increase the default memory heap size on the vRealize Orchestrator Appliance.

    Request a Product Feature

    To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

    Feedback

    • 2 Ratings

    Did this article help you?
    This article resolved my issue.
    This article did not resolve my issue.
    This article helped but additional information was required to resolve my issue.

    What can we do to improve this information? (4000 or fewer characters)




    Please enter the Captcha code before clicking Submit.
    • 2 Ratings
    Actions
    KB: