VMware {code} Community
Trip201110141
Contributor
Contributor
‎02-13-2017 01:52 PM

Virgo server on Windows dev box is reading \var\lib\vmware\vsphere-client\webclient.properties

When I start the Virgo server using <vsphere-client-sdk>\server\bin\startup.bat, it starts up no problem and seems to read the webclient.properties in C:\ProgramData\VMware\vSphere Web Client.  When I start the Virgo server from Eclipse, it fails to start (error msg below) and looking at vsphere_client_virgo.log it appears to be trying to read from \var\lib\vmware\vsphere-client\webclient.properties. Clearly I've misconfigured something, but I'm not sure what.  Does anyone have any idea what configuration setting/element I need to correct so that I can launch the Virgo server from the Eclipse IDE?  Thanks.

Eclipse server console:

[2017-02-13T07:35:25.355-05:00] [ERROR] region-dm-3                   <AG0000E> Application context creation failure for bundle 'com.vmware.vimservices' version '6.0.0'. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManager': 
Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManagerImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: 
Cannot resolve reference to bean 'ssoServiceImpl' while setting constructor argument; 
   nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoServiceImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean 'ssoLocatorImpl' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoLocatorImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl]: Constructor threw exception; nested exception is java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.

vsphere_client_virgo.log when starting Virgo server using startup.bat:
[2017-02-13T13:11:45.907-05:00] [INFO ] region-dm-9                   c.vmware.vise.util.client.configuration.ConfigurationServiceImpl  Reloading config file: C:\ProgramData\VMware\vSphere Web Client\webclient.properties 

vsphere_client_virgo.log when starting Virgo server from Eclipse:
[2017-02-13T16:29:32.271-05:00] [INFO ] region-dm-9                   c.vmware.vise.util.client.configuration.ConfigurationServiceImpl  Reloading config file: \var\lib\vmware\vsphere-client\webclient.properties 

 

 

[2017-02-13T07:35:25.355-05:00] [ERROR] region-dm-3                   <AG0000E> Application context creation failure for bundle 'com.vmware.vimservices' version '6.0.0'. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManager': 
Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManagerImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: 
Cannot resolve reference to bean 'ssoServiceImpl' while setting constructor argument; 
   nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoServiceImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean 'ssoLocatorImpl' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoLocatorImpl' defined in URL [bundleentry://175.fwk710714889/META-INF/spring/bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl]: Constructor threw exception; nested exception is java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.
Reply
7 Replies
laurentsd
VMware Employee
VMware Employee
‎02-14-2017 10:06 AM

The location of webclient.properties is controlled by the env variable VMWARE_CFG_DIR.  Check if you redefined that value in Eclipse.

Reply
0 Kudos
Trip201110141
Contributor
Contributor
‎02-14-2017 12:36 PM

I found VMWARE_CFG_DIR under the environment tab of Edit Launch Configuration Properties.  I set it to "C:\ProgramData\VMware\vSphere Web Client" (no quotes), then exited and restarted Eclipse.  When I tried to start the Virgo Server I got the same error (below) and the vsphere_client_virgo.log (attached) still has the entry

[2017-02-14T15:14:29.104-05:00] [INFO ] region-dm-9

c.vmware.vise.util.client.configuration.ConfigurationServiceImpl  Reloading config file: \var\lib\vmware\vsphere-client\webclient.properties

Is there somewhere else I need to set it?

[2017-02-14T15:14:38.300-05:00] [ERROR] region-dm-3               <AG0000E> Application context creation failure for bundle 'com.vmware.vimservices' version '6.0.0'. org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManager': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManagerImpl' defined in URL [bundleentry://175.fwk707610042/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean 'ssoServiceImpl' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoServiceImpl' defined in URL [bundleentry://175.fwk707610042/META-INF/spring/bundle-context.xml]: Cannot resolve reference to bean 'ssoLocatorImpl' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoLocatorImpl' defined in URL [bundleentry://175.fwk707610042/META-INF/spring/bundle-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl]: Constructor threw exception; nested exception is java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1455)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)

    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)

    at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)

    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)

    at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)

    at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)

    at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:589)

    at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:925)

    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)

    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)

    at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)

    at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)

    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)

    at org.eclipse.virgo.kernel.agent.dm.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:95)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

vsphere_client_virgo.log.zip
Reply
0 Kudos
Trip201110141
Contributor
Contributor
‎02-15-2017 06:41 AM

Tried changing VMWARE_CFG_DIR to C:\ProgramData\VMware\vsphere-client, same results.

Tried changing VMWARE_CFG_DIR to C:\ProgramData\VMware\vCenterServer\cfg, same results.

Reply
0 Kudos
laurentsd
VMware Employee
VMware Employee
‎02-15-2017 08:05 PM

It's hard to provide more help without seeing your environment. 

To unblock yourself I suggest that you use the command line to start Virgo under /server/bin, instead of starting it in Eclipse.

You can still use Eclipse for debugging (use a Java remote debugging configuration) and you can still deploy your plugin .war and .jar bundles easily. They can be hot-deployed by copying the files directly in /server/pickup

Reply
0 Kudos
_vladi_
VMware Employee
VMware Employee
‎02-16-2017 03:09 AM

Here are a few thing you could check:

- On 6.5 Web Client VMWARE_CFG_DIR should point to C:\ProgramData\VMware\vCenterServer\cfg. The store.jks of your vCenter should be in this folder and the webclient.properties should be in C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\.

- Looking at the provided logs it might be that the ComponentManager URL is missing or wrong. Please check if the webclient.properties file contains such line: cm.url=https://<YOUR_VCENTER_DNS_NAME>/cm/sdk/

- Have a look at your server/configuration/tomcat-server.xml file. It should contain the right path to your store.jks like this: keystoreFile="C:/ProgramData/VMware/vCenterServer/cfg/store.jks"

Reply
jvitorino
Enthusiast
Enthusiast
‎11-20-2017 11:02 AM

Did you ever find a solution to this error?  I'm having the same issue.  Thanks!

Reply
0 Kudos
_vladi_
VMware Employee
VMware Employee
‎11-21-2017 12:32 AM

This is not a product issue but a problem in the local dev setup. Please have a look at all the recommendations and if it still does not work provide some details: e.g. the location/content of webclient.properties, location of store.jks, etc.

Cheers,

Vladi

Reply
0 Kudos