Hi All,
We are facing issue after upgrading the vCenter server 6.0 u2 to u3. In the vSphere web client, our plugin is getting the resource URL protocol as "bundleresource" where as in all the previous versions of vCenter server, the resource URL protocol is "File".
But in case of fresh installation of vCenter server 6.0 update 3, plugin works fine as it gets the expected resource URL as ”File”. So we checked the web client server configuration file of both the servers, one that has been upgraded from update 2 and the other one which is a fresh installation.
Wrapper.conf of vCenter server 6.0 u3 web client server fresh installed: <image1.png>
Wrapper.conf of vCenter server 6.0 u3 web client upgraded from update 2 :<image2.png>
Then we checked the file path to confirm if the jar version is correct or not which we found as: <image3.png>
So the web client server is still referring to the older jars which are even not available in the file path. We changed the wrapper.conf file to refer the updated jar version and restarted the web client server.
set.OSGI_CLASSPATH=file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.nano.authentication_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.equinox.launcher_1.3.0.v20120308-1358.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.nano.shutdown_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.util.env_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/lib/org.eclipse.virgo.kernel.equinox.extensions_3.6.4.RELEASE.jar,file:/usr/lib/vmware-virgo/server/plugins/org.eclipse.osgi_3.8.2.v20130124-134944.jar
After login to the web client, we can now see the Plugin in the home page and it’s working fine now. The resource URL protocol is coming as "File" now.
We are not sure why VMware upgrade path didn’t update the wrapper.conf to refer the updated jar.
Thanks,
Sourav