org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.

Apereo Issues | Faizan Ahmed | 10 years ago
  1. 0

    Circular reference Exception is occuring in the log. How to Produce it: I tried to configure CAS with uP3 and ran into this problem. Trying PAGS can also cause this exception Following is the Stack trace ERROR [main] [localhost].[/uP3] Dec/17 15:24:31.750 - Exception sending context initialized event to listener instance of class org.jasig.portal.problem.ExceptionConfigurationListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDao' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.persondirectory.mappedPersonAttributeDaoTarget' while setting bean property 'mappedUserAttributeProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDaoTarget' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletApplicationDefinitionRegistry' while setting bean property 'portletApplicationDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDaoTarget' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletApplicationDefinitionRegistry' while setting bean property 'portletApplicationDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:423) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)

    Apereo Issues | 10 years ago | Faizan Ahmed
    org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.
  2. 0

    Circular reference Exception is occuring in the log. How to Produce it: I tried to configure CAS with uP3 and ran into this problem. Trying PAGS can also cause this exception Following is the Stack trace ERROR [main] [localhost].[/uP3] Dec/17 15:24:31.750 - Exception sending context initialized event to listener instance of class org.jasig.portal.problem.ExceptionConfigurationListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDao' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.persondirectory.mappedPersonAttributeDaoTarget' while setting bean property 'mappedUserAttributeProvider'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDaoTarget' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletApplicationDefinitionRegistry' while setting bean property 'portletApplicationDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.persondirectory.mappedPersonAttributeDaoTarget' defined in ServletContext resource [/WEB-INF/beans/portal/person-directory.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletApplicationDefinitionRegistry' while setting bean property 'portletApplicationDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletApplicationDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionControlFactory' while setting bean property 'portletDefinitionControlFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionControlFactory' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.transientPortletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'portal.registries.transientPortletDefinitionRegistry' defined in ServletContext resource [/WEB-INF/beans/portal/registries.xml]: Cannot resolve reference to bean 'portal.registries.portletDefinitionRegistry' while setting bean property 'portletDefinitionRegistry'; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. Caused by: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example. at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:423) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)

    Apereo Issues | 10 years ago | Faizan Ahmed
    org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.
  3. 0

    Circular Reference in Spring

    manning.com | 9 months ago
    org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'serversService': Bean with name 'serversService' has been injected into other beans [appDataService] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Why Spring circular reference for Autowire issue on Production Environment Only?

    Stack Overflow | 10 months ago | Vishnu Katpure
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSearchService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private in.grex.server.dto.mapper.CustomGrexMapper in.grex.server.search.DataSearchServiceImpl.customGrexMapper; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'customGrexMapper': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private in.grex.server.services.organizationassociation.OrganizationAssociationService in.grex.server.dto.mapper.CustomGrexMapperImpl.organizationAssociationService; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'organizationAssociationService': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private in.grex.server.services.organization.OrganizationService in.grex.server.services.organizationassociation.OrganizationAssociationServiceImpl.organizationService; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'organizationService': Bean with name 'organizationService' has been injected into other beans [utilityService,organizationUserService,companyService,messageService,investorService] in its raw version as part of a circular reference, but has eventually been wrapped. This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.
  6. 0

    Spring Data JPA repository dependency, Autowiring a Jpa repository sub-class inside a custom repository

    Stack Overflow | 2 years ago | Jeff
    org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'personRepositoryCustomImpl': Bean with name 'personRepositoryCustomImpl' has been injected into other beans [personRepository] in its raw version as part of a circular reference, but has eventually been wrapped. This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.springframework.beans.factory.BeanCurrentlyInCreationException

      Error creating bean with name 'portal.registries.portletDefinitionRegistry': Bean with name 'portal.registries.portletDefinitionRegistry' has been injected into other beans [portal.registries.portletDefinitionFactory] in its raw version as part of a circular reference, but has eventually been wrapped (for example as part of auto-proxy creation). This means that said other beans do not use the final version of the bean. This is often the result of over-eager type matching - consider using 'getBeanNamesOfType' with the 'allowEagerInit' flag turned off, for example.

      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean()
    2. Spring Beans
      AbstractBeanFactory$1.getObject
      1. org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:423)
      2. org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245)
      2 frames