org.springframework.beans.factory.BeanCurrentlyInCreationException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • 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)
    via by Faizan Ahmed,
  • 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)
    via by Faizan Ahmed,
  • Circular Reference in Spring
    via by Unknown author,
  • Re: Usergrid unabe to start
    via by Samuel Ngoda,
  • Re: Usergrid unabe to start
    via by Samuel Ngoda,
  • Re: Usergrid unabe to start
    via by Samuel Ngoda,
    • 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)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,