VMware {code} Community
RuchaAgsar
Contributor
Contributor

vsphere web client SDK 6.0 java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.

Hi,

     When starting virgo webserver, I am getting below exception.

I do have generated webclient.properties and store.jks and pasted them under C:\ProgramData\VMware\vSphere Web Client on my local dev machine.

tool versions that I am using  are:

vsphere web client version: vimclients-public-sdk-6.0.0.2503177.zip (vsphere-client-sdk-version.xml shows build as 2502242)

vCenter version: VMware-VIMSetup-all-6.0.0-2503529.iso

Eclipse version: Eclipse Java EE IDE Juno Service Release 2

JDK version: 1.7.0_71

Virgo tools installed from URL: http://dist.springsource.com/release/TOOLS/virgo-ide

I have followed steps defined in SDK-Setup.html that I got with the SDK build.

webclient.properties does have cm.url defined.

Attached is the virgo logs from vsphere-client-sdk eclipse setup

Please kindly let me know if I am missing anything.

[2015-02-17T13:13:04.219-05:00] [INFO ] system-artifacts              <DE0004I> Starting bundle 'com.vmware.extensionservice' version '6.0.0'.

[2015-02-17T13:13:04.358-05:00] [INFO ] start-signalling-1            <DE0005I> Started bundle 'com.vmware.extensionservice' version '6.0.0'.

[2015-02-17T13:13:04.406-05:00] [INFO ] system-artifacts              <DE0000I> Installing bundle 'com.vmware.tools.delaydeployer' version '6.0.0'.

[2015-02-17T13:13:04.419-05:00] [INFO ] system-artifacts              <DE0001I> Installed bundle 'com.vmware.tools.delaydeployer' version '6.0.0'.

[2015-02-17T13:13:04.726-05:00] [INFO ] system-artifacts              <DE0004I> Starting bundle 'com.vmware.tools.delaydeployer' version '6.0.0'.

[2015-02-17T13:13:04.840-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0000I> Installing bundle 'com.vmware.help' version '6.0.0'.

[2015-02-17T13:13:05.018-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0001I> Installed bundle 'com.vmware.help' version '6.0.0'.

[2015-02-17T13:13:05.026-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0004I> Starting bundle 'com.vmware.help' version '6.0.0'.

[2015-02-17T13:13:05.123-05:00] [INFO ] start-signalling-1            <DE0005I> Started bundle 'com.vmware.help' version '6.0.0'.

[2015-02-17T13:13:05.297-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0000I> Installing bundle 'com.vmware.store' version '6.0.0'.

[2015-02-17T13:13:05.325-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0001I> Installed bundle 'com.vmware.store' version '6.0.0'.

[2015-02-17T13:13:05.334-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0004I> Starting bundle 'com.vmware.store' version '6.0.0'.

[2015-02-17T13:13:05.477-05:00] [INFO ] start-signalling-1            <DE0005I> Started bundle 'com.vmware.store' version '6.0.0'.

[2015-02-17T13:13:07.430-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0000I> Installing bundle 'com.vmware.dataservices' version '6.0.0'.

[2015-02-17T13:13:07.448-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0001I> Installed bundle 'com.vmware.dataservices' version '6.0.0'.

[2015-02-17T13:13:07.457-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0004I> Starting bundle 'com.vmware.dataservices' version '6.0.0'.

[2015-02-17T13:13:07.700-05:00] [INFO ] start-signalling-1            <DE0005I> Started bundle 'com.vmware.dataservices' version '6.0.0'.

[2015-02-17T13:13:08.988-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0000I> Installing bundle 'com.vmware.vimservices' version '6.0.0'.

[2015-02-17T13:13:09.712-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0001I> Installed bundle 'com.vmware.vimservices' version '6.0.0'.

[2015-02-17T13:13:09.721-05:00] [INFO ]  TCP Connection(4)-127.0.0.1  <DE0004I> Starting bundle 'com.vmware.vimservices' version '6.0.0'.

[2015-02-17T13:13:12.806-05:00] [ERROR] region-dm-5                   <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://173.fwk638798081/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://173.fwk638798081/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://173.fwk638798081/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(ThreadPoolExecutor.java:1145)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

  at java.lang.Thread.run(Thread.java:745)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManagerImpl' defined in URL [bundleentry://173.fwk638798081/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://173.fwk638798081/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://173.fwk638798081/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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)

  at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)

  at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean.afterPropertiesSet(OsgiServiceFactoryBean.java:198)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)

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

  ... 17 common frames omitted

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoServiceImpl' defined in URL [bundleentry://173.fwk638798081/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://173.fwk638798081/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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)

  at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)

  at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:323)

  ... 31 common frames omitted

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoLocatorImpl' defined in URL [bundleentry://173.fwk638798081/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.ConstructorResolver.autowireConstructor(ConstructorResolver.java:288)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:323)

  ... 43 common frames omitted

Caused by: 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.BeanUtils.instantiateClass(BeanUtils.java:162)

  at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)

  ... 52 common frames omitted

Caused by: java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.

  at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getServiceUrl(ComponentManagerServiceImpl.java:108)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl$CMUpdateTracker.<init>(SsoCmLocatorImpl.java:136)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.<init>(SsoCmLocatorImpl.java:47)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

  at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)

  ... 54 common frames omitted

[2015-02-17T13:13:12.807-05:00] [ERROR] start-signalling-1            <DE0006E> Start failed 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://173.fwk638798081/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://173.fwk638798081/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://173.fwk638798081/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(ThreadPoolExecutor.java:1145)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

  at java.lang.Thread.run(Thread.java:745)

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'cloudVmServiceManagerImpl' defined in URL [bundleentry://173.fwk638798081/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://173.fwk638798081/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://173.fwk638798081/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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)

  at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)

  at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.eclipse.gemini.blueprint.service.exporter.support.OsgiServiceFactoryBean.afterPropertiesSet(OsgiServiceFactoryBean.java:198)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1514)

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

  ... 17 common frames omitted

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoServiceImpl' defined in URL [bundleentry://173.fwk638798081/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://173.fwk638798081/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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:329)

  at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:107)

  at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:323)

  ... 31 common frames omitted

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ssoLocatorImpl' defined in URL [bundleentry://173.fwk638798081/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.ConstructorResolver.autowireConstructor(ConstructorResolver.java:288)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)

  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)

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

  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.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:323)

  ... 43 common frames omitted

Caused by: 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.BeanUtils.instantiateClass(BeanUtils.java:162)

  at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)

  ... 52 common frames omitted

Caused by: java.lang.NullPointerException: The URL of the VMware Component Manager cannot be empty.

  at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getServiceUrl(ComponentManagerServiceImpl.java:108)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl$CMUpdateTracker.<init>(SsoCmLocatorImpl.java:136)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.<init>(SsoCmLocatorImpl.java:47)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

  at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)

  ... 54 common frames omitted

32 Replies
laurentsd
VMware Employee
VMware Employee

Check the value of cm.url in webclient.properties, it sounds like it is not a valid URL.

It must have the format

cm.url = https://HOST_DNS_NAME/cm/sdk/

for the host where vSphere is installed.

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

Hi Laurent,

                Thank you very much for your reply.

Below are the contents of webclient.properties.

cm.url=https://<Host_dns_name>/cm/sdk/


I am able to do remote desktop to <Host_dns_name> and ping command is also working.

https URL is also working. It points to vSphere 6.0 machine.

In the attached vsphere_client_virgo.log, I see below exception. though afd.disabled=true is mentioned in webclient.properties.

I have generated webclient.properties and store.jks on vsphere machine 6.0 itself using vsphere-client-sdk\tools\Dev setup scripts (vCenter registration)\dev-setup.bat.

I am not sure, is the webclient.properties not getting used?

Do I need to do any other configuration to to pick webclient.properties from C:\ProgramData\VMware\vSphere Web Client ?

I am not sure is it because of URL https certificate issue?

In vsphere 5.5 plugin I used to put client.properties under virgo server configuration.

For 6.0 I did not add any client.properties.

Sorry for the long message. I can provide you other details if you need.

Exception in logs:

[2015-02-17T15:47:47.437-05:00] [ERROR] region-dm-5                   com.vmware.vise.vim.cm.impl.AfdCMSource                           Error when talking to afd client java.lang.ExceptionInInitializerError: null

  at com.vmware.af.VmAfClient.getCMLocation(VmAfClient.java:47)

  at com.vmware.vise.vim.cm.impl.AfdCMSource.getCMUrl(AfdCMSource.java:62)

  at com.vmware.vise.vim.cm.impl.AfdCMSource.getServiceUri(AfdCMSource.java:32)

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

webclient.properties:

#

# Generated webclient.properties for dev environments.

# Copy this file to the right location along with the generated store.jks (see path below).

#

# The keystore and cm.url settings allow to connect your local Web Client server to your VCSA

# or vCenter for Windows. For additional properties see the content of webclient.properties

# in /etc/vmware/vsphere-client or C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\

#

# Do not change.

afd.disabled=true

keystore.jks.password=vmw@re

#

# Set the correct value of keystore.jks.path based on your dev OS.

# Mac OS: /var/lib/vmware/vsphere-client/store.jks

# Windows: C:/ProgramData/VMware/vSphere Web Client/store.jks

keystore.jks.path=C:/ProgramData/VMware/vSphere Web Client/store.jks

#

# ComponentManager url with the DNS name of your vCenter Server for Windows host.

cm.url=https://<Host_dns_name>/cm/sdk/

#

# Other useful webclient.properties flags for a local dev setup

show.allusers.tasks=true

large.inventory.mode=true

aggregationThreshold.VirtualMachine=100

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

AFD exception though afd.disabled=true in webclient.properties.

[2015-02-18T11:49:15.905-05:00] [INFO ] region-dm-5                   t.i.VmodlContextImpl$NonValidatingClassPathXmlApplicationContext  Closing com.vmware.vim.vmomi.core.types.impl.VmodlContextImpl$NonValidatingClassPathXmlApplicationContext@50380d4: startup date [Wed Feb 18 11:49:15 EST 2015]; root of context hierarchy

[2015-02-18T11:49:15.905-05:00] [INFO ] region-dm-5                   o.s.beans.factory.support.DefaultListableBeanFactory              Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@1c82368a: defining beans [context]; root of factory hierarchy

[2015-02-18T11:49:15.931-05:00] [INFO ] region-dm-5                   com.vmware.vise.vim.cm.impl.AfdCMSource                           Creating vm afd client at localhost

[2015-02-18T11:49:16.049-05:00] [ERROR] region-dm-5                   com.vmware.vise.vim.cm.impl.AfdCMSource                           Error when talking to afd client java.lang.ExceptionInInitializerError: null

  at com.vmware.af.VmAfClient.getCMLocation(VmAfClient.java:47)

  at com.vmware.vise.vim.cm.impl.AfdCMSource.getCMUrl(AfdCMSource.java:62)

  at com.vmware.vise.vim.cm.impl.AfdCMSource.getServiceUri(AfdCMSource.java:32)

  at com.vmware.vise.vim.cm.impl.ComponentManagerLocator.getServiceUri(ComponentManagerLocator.java:39)

  at com.vmware.vise.vim.cm.impl.ComponentManagerServiceImpl.getServiceUrl(ComponentManagerServiceImpl.java:106)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl$CMUpdateTracker.<init>(SsoCmLocatorImpl.java:136)

  at com.vmware.vise.vim.security.sso.impl.SsoCmLocatorImpl.<init>(SsoCmLocatorImpl.java:47)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)

  at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147)

  at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121)

  at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280)

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

I see that I am also facing the same issue from the forum https://communities.vmware.com/thread/499832

May be correction to above:

The vCenter summary on vsphere web client shows build number 2503372.

I also see AFD exception is caused by:

Caused by: java.lang.IllegalStateException: Path "C:\Program Files\VMware\CIS\vmdird" does not exist

  at com.vmware.af.interop.NativeAdapter.<clinit>(NativeAdapter.java:99)

  ... 66 common frames omitted

Thanks.

Reply
0 Kudos
laurentsd
VMware Employee
VMware Employee

> Path "C:\Program Files\VMware\CIS\vmdird" does not exist

I don't know what this error means, never ran into this before.  Will get back to you if I find anything,

RuchaAgsar
Contributor
Contributor

Thanks Laurent. I am also going through instructions again. I will post if I manage to resolve the issue.

Thanks again.

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

Hi Laurent,

                 After reinstalling everything. it seems to work.

I could not reproduce the issue later. Sorry for the trouble caused.

I have marked it resolved.

Thanks,

Rucha

Reply
0 Kudos
laurentsd
VMware Employee
VMware Employee

No problem, glad it is solved.

Reply
0 Kudos
ynbrowntea
Contributor
Contributor

I am seeing the same issue.

Caused by: java.lang.IllegalStateException: Path "C:\Program Files\VMware\CIS\vmdird" does not exist

  at com.vmware.af.interop.NativeAdapter.<clinit>(NativeAdapter.java:99)

  ... 66 common frames omitted

@RuchaAgsarRuchaAgsar, did you reinstall everything on your dev box? Or even the vCenter?

Thanks!

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

Hi,

I did not reinstall vCenter.

Below are the steps that may help you.

1. If you are moving from 5.5, please make sure that folder C:\ProgramData\VMware\vSphere Web Client does not contain data from 5.5 setup.

2. Not sure how much it can help, but I purposefully set eclipse -> wondow preferences -> java -> compiler -> generate .class compatibility  and  source compatibility to 1.6 before configuring anything in eclipse.

3. Before adding virgo web server to eclipse after downloading Virgo tools, paste  generated webclient.properties and store.jks from dev-setup.bat to C:\ProgramData\VMware\vSphere Web Client. If running vsphere-client-sdk\server\bin\startup.bat can start virgo web server properly, then the problem can be with eclipse. Please make sure to generate the two files on vCenter server 6.0.

4. After that add Virgo server from servers tab.


Please let me know if it can resolve the issue.


Thanks,

Rucha

ynbrowntea
Contributor
Contributor

@RuchaAgsar

Hi Rucha,

Thanks a lot for your reply!

After running vsphere-client-sdk\server\bin\startup.bat to start virgo web server, I can start my virgo server in Eclipse successfully. It's interesting how that can fix the problem. I guess there are some dependencies that eclipse was not able to resolve?

Thanks a lot for your help!

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

Hi Laurent and ynbrowntea,

                                 Even I noticed that after starting vsphere-client-sdk\server\bin\startup.bat , eclipse server is starting properly.

Not sure if any environment variable \ configuration is getting set.

Hi ynbrowntea,

                         No problem at all. Thanks.

Thanks,

Rucha

Reply
0 Kudos
laurentsd
VMware Employee
VMware Employee

I don't think this is related to old 5.5 files.

Are you saying that you get the error "Path "C:\Program Files\VMware\CIS\vmdird" does not exist" when you first start Virgo from Eclipse, whether or not you had perform the vCenter registration setup before? (i.e. generate store.jks and webclient.properties with dev-setup.bat and copy them in C:/ProgramData/VMware/vSphere Web Client )

And that this error gets resolved only by running server/bin/startup.bat?

Reply
0 Kudos
RuchaAgsar
Contributor
Contributor

Hi Laurent,

                  As you said it might not be related to old 5.5 files.

You would know better since I don't know internals.  I had 5.5 setup earlier. 

Yes, I got error irrespective of generating store.jks and webclient.properties and adding it under C:/ProgramData/VMware/vSphere Web Client.

Yes it seems to get resolved by running startup.bat. Don't know was it because of running virgo first and then pasting contents?

But it is related configuring Virgo runtime in eclipse. I can provide you more details if you need.

Also it seems to occur just the time before running startup.bat. not anytime later Smiley Happy.

Thanks.

Reply
0 Kudos
nishtek
Contributor
Contributor

HI Laurentsd, i am facing the same problem as stated in thread. even i tried every possible sollution discussed in this thread. but m still facing the issue. my logs are same as rusasgar. like null pointer exception and the directory not found error.

I already tried reinstalling the whole setup again and again many times.

my dns name of the windows host  machine in the cm.url is also correct.

i even tried mannually starting virgo server which failed.

can you please help me here.

Reply
0 Kudos
nishtek
Contributor
Contributor

one thing is that i dont have a dns server so i am locally resolving the dns name through host file in drivers/etc . does that make any difference. i am able to ping that dns name from any where on my network.

Reply
0 Kudos
prmsvm
Contributor
Contributor

Hi,

I am also getting same error, even though I followed RuchaAgsar steps.

Is it possible to use One vcenter server(webclient.properties, store.jks) for two dev setup

Reply
0 Kudos
laurentsd
VMware Employee
VMware Employee

> Is it possible to use One vcenter server(webclient.properties, store.jks) for two dev setup

The webclient.properties and store.jks files generated by the dev-setup script on a vCenterA host machine are unique to that vCenterA + SSO environment.  If you want to use the same dev setup to connect to another vCenterB server you need to have that vCenterB connect to the same SSO server as vCenterA.

Reply
0 Kudos
prmsvm
Contributor
Contributor

Hi laurentsd,

Sorry, I did not explain the scenario clearly.

We have one vcenter server machine(Vcenter A) and two dev(Machine A, Machine B) environment.

Using dev-setup.bat , we generated those two files in vcenter server(Vcenter A).

Is it possible to use the same two files in Machine B to connect to the vcenter server(Vcenter A)?

Reply
0 Kudos