Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not allow eager init when getting beans by type to resolve Configurers for Annotation configuration [DATAGEODE-121] #167

spring-projects-issues opened this issue Jun 13, 2018 · 0 comments


Copy link

@spring-projects-issues spring-projects-issues commented Jun 13, 2018

John Blum opened DATAGEODE-121 and commented

This change will disable the allowEagerInit flag when calling the ListableBeanFactory.getBeansOfType(:Class, includeNonSingletons:boolean, allowEagerInit:boolean) searching for SDG *Configurers defined in the Spring container.

It is possible, with allowEagerInit set to true that a BeanCurrentlyInCreationException can be thrown on Spring container initialization, depending on the Configuration applied along with the beans declared/scanned/registered by the user in his/her Spring application

Affects: 2.0.7 (Kay SR7)

Backported to: 2.0.8 (Kay SR8)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.