Attempting to view performance graphs in vCommander®, you encounter the message Unable to retrieve performance graph. See vCommander.log for further information.
In the vCommander log file, you locate an error similar to the following:
2017-03-21 10:40:30,643 [http-bio-443-exec-9] ERROR - Processing proxy passthrough java.io.IOException: Server returned HTTP response code: 503 for URL: https://your_vCenter:443/statsreport/StatsChartServlet?dummy&entity=VirtualMachine:vm-13709&entityName=TK-TRD-AEBUEN&sessionId=fbf52474075034516f972ac1a7241e8497125d02&serviceUrl=https://your-vCenter/sdk&chartDesc=vmNetReceivedTransmittedMbpsReport&topN=0&width=430&height=380&timeRangeType=realtime&timeRangeStart=1490103625627&timeRangeEnd=1490107225627&timeZone=GMT-04%3A00&locale=en_US&colorProvider=com.vmware.vim.stats.webui.chart.text.ChartColorProvider at sun.reflect.GeneratedConstructorAccessor428.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at com.embotics.vlm.proxy.servlet.ProxyServlet.doPost(ProxyServlet.java:207) at com.embotics.vlm.proxy.servlet.ProxyServlet.doGet(ProxyServlet.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:624) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:620) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745)
Solution
This issue is occurring because performance charts have been disabled by your vCenter administrators.
This may potentially have happened to deal with VMWare Security Advisory WSA-2017-0004.6: VMware product updates resolve remote code execution vulnerability via Apache Struts 2. The only current known workaround requires that the performance charts be turned off.