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

Logging in to the vCenter Server through the vSphere Web client fails after upgrading vCloud Networking and Security to NSX for vSphere 6.x (2094106)

  • 0 Ratings

Symptoms

  • After upgrading from vCloud Networking and Security to NSX for vSphere, vCenter Server and the Web Client are unstable
  • High CPU and memory on the vCenter Server host are seen even when no tasks are running in vCenter Server
  • Logging in to the vCenter Server or Web Client fails

Cause

This issue occurs when NSX for vSphere uses a Web Client plug-in to manage network virtualization.

Resolution

To resolve this issue, optimize the performance with NSX, vCenter Server minimums for CPU, memory, and disk must be followed carefully. For more information, see ESXi/ESX configuration Maximums (1003497).
In addition, the Java heap size of the Web client must be increased.
You can adjust the JVM maximum heap size for vCenter Server, vCenter Single Sign-On, vCenter Inventory Service, and Profile-Driven Storage Service.

This table provides the JVM heap size recommendations:

vCenter Server 5.1:
vCenter Server Inventory VMware VirtualCenter Management Webservices (tc Server) Inventory Service Profile-Driven Storage Service
Small inventory (1-100 hosts or 1-1000 virtual machines) 1 GB 3 GB 512 MB
Medium inventory (100-400 hosts or 1000-4000 virtual machines) 2 GB 6 GB 1 GB
Large inventory (More than 400 hosts or 4000 virtual machines) 3 GB 12 GB 2 GB



vCenter Server 5.5:

vCenter Server Inventory VMware VirtualCenter Management Webservices (tc Server) Inventory Service Profile-Driven Storage Service
Small inventory (1-100 hosts or 1-1000 virtual machines) 512 MB 3 GB 1 GB
Medium inventory (100-400 hosts or 1000-4000 virtual machines) 512 MB 6 GB 2 GB
Large inventory (More than 400 hosts or 4000 virtual machines) 1024 MB 12 GB 4 GB



Note: After adjusting the JVM heap size in the wrapper.conf file, it is recommended to restart the VirtualCenter Management Web services. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Java setting options and file locations for vSphere services

  • VirtualCenter Management WebServices

    Configuration file location:

    installation_directory\VMware\Infrastructure\tomcat\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Single Sign-On (vSphere 5.1)

    Configuration file location:

    installation_directory\VMware\Infrastructure\SSOServer\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Single Sign-On (vSphere 5.5)

    Configuration file location:

    installation_directory\ProgramData\VMware\CIS\runtime\VMwareSTS\conf\wrapper.conf

    Heap size parameter:

    wrapper.java.additional.9="-Xmxheap_sizeM"

  • vCenter Inventory Service

    Configuration file location:

    installation_directory\VMware\Infrastructure\Inventory Service\conf\wrapper.conf

    Heap size parameter:

    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=heap_size


  • vSphere Profile-Driven Storage

    Configuration file location:

    installation_directory\VMware\Infrastructure\Profile-Driven Storage\conf\wrapper.conf

    Heap size parameter:

    # Maximum Java Heap Size (in MB)
    wrapper.java.maxmemory=heap_size


  • vSphere Web Client

    Configuration file location:

    installation_directory\Program Files\VMware\Infrastructure\vSphereWebClient\server\bin\service\conf\wrapper.conf

    Heap size parameter:

    ########
    # JVM Memory
    ########
    wrapper.java.maxmemory=heap_size


  • VMware Log Browser

    Configuration file location:

    installation_directory\Program Files\VMware\Infrastructure\vSphereWebClient\logbrowser\conf\wrapper.conf

    Heap size parameter:

    ########
    # JVM Memory
    ########
    wrapper.java.maxmemory=heap_size
For more information, see:

Additional Information

In vCenter Server 5.1, VMware Tomcat Server settings can no longer be configured through the Windows user interface at Start > Programs > VMware > VMware Tomcat.

vCenter Server 5.1 uses VMware vFabric tc Server, an enterprise version of Apache Tomcat 7. Tomcat version 7 does not provide a control panel in the Windows user interface. Instead, you must configure Tomcat by editing configuration files manually.
Note: Earlier versions of vCenter Server 5.1 uses Tomcat Version 6.

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

  • 0 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.
  • 0 Ratings
Actions
KB: