This issue is resolved in VMware vCenter Server 6.0 Update 2, available at VMware Downloads
To work around this issue, increase or add the max HTTP header size in the server.xml file of the performance charts service.
- Create a copy of the C:\ProgramData\VMware\vCenterServer\data\perfcharts\tc-instance\conf\server.xml file on vCenter Server.
Note: Path in VCSA, /usr/lib/vmware-perfcharts/tc-instance/conf/server.xml
- Open the server.xml file using a plain text editor.
- In the and , sections search for the port="${bio.http.port}" entry.
Note: Add the entry if it is not present.
- Modify both entries to maxHttpHeaderSize="65536".
For example:
<Connector address="127.0.0.1" acceptCount="300" maxThreads="300" connectionTimeout="20000" executor="tomcatThreadPool" maxKeepAliveRequests="15" port="${bio.http.port}" maxHttpHeaderSize="65536" protocol="org.apache.coyote.http11.Http11Protocol"/> <Connector address="::1" acceptCount="300" maxThreads="300" connectionTimeout="20000" executor="tomcatThreadPool" maxKeepAliveRequests="15" port="${bio.http.port}" maxHttpHeaderSize="65536" protocol="org.apache.coyote.http11.Http11Protocol"/>
Note: The entry is case sensitive.
- Restart the performance charts service with these commands:
- service-control --stop vmware-perfcharts
- service-control --start vmware-perfcharts
Note:Path for service-control C:\Program Files\VMware\vCenter Server\bin
- Log in to the vSphere Web Client and retry the performance charts.