You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rayees Namathponnan (JIRA)" <ji...@apache.org> on 2013/06/25 07:18:21 UTC

[jira] [Created] (CLOUDSTACK-3178) [vmsync] Failed to start management server with vmsync non-oss build

Rayees Namathponnan created CLOUDSTACK-3178:
-----------------------------------------------

             Summary: [vmsync] Failed to start management server with vmsync non-oss build
                 Key: CLOUDSTACK-3178
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3178
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Install and Setup
    Affects Versions: 4.2.0
         Environment: vmsync branch 
            Reporter: Rayees Namathponnan
             Fix For: 4.2.0


Management server failed to start with non-oss build

Asa1000vMapDaoImpl,CiscoVNMC,bigSwitchVnsDaoImpl,bigSwitchVnsElement,MidoNetGuestNetworkGuru,MidoNetElement,userAuthenticators,userPasswordEncoders,securi
tyCheckers,resourceDiscoverers,haInvestigators,haFenceBuilders,deploymentPlanners,podAllocators,hostAllocators,storagePoolAllocators,ipDeployers,dhcpProvi
ders,networkGurus,networkElements,HostAntiAffinityProcessor,affinityProcessors,DedicatedResourceManagerImpl,ExplicitDedicationProcessor,org.springframewor
k.context.annotation.ConfigurationClassPostProcessor$ImportAwareBeanPostProcessor#0]; root of factory hierarchy
2013-06-25 01:12:53,756 ERROR [web.context.ContextLoader] (main:null) Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'actionEventUtils': Injection of autowired dependencies failed; nes
ted exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: com.cloud.event.dao.EventDao com.cloud.event.ActionEve
ntUtils.eventDao; nested exception is org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [com.cloud.netapp.dao.LunDaoImpl]
for bean with name 'lunDaoImpl' defined in class path resource [nonossComponentContext.xml]; nested exception is java.lang.ClassNotFoundException: com.clo
ud.netapp.dao.LunDaoImpl
        at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcesso
r.java:287)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517)
        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:609)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:469)
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira