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
Bean creation fails with StackOverflowError after upgrading from 5.1.13 to 5.2.7 #25546
Comments
Please provide a minimal example application that reproduces the problem you have encountered -- for example, by creating a project at https://start.spring.io and sharing it via an online Git repo or a downloadable zip file. Thanks |
Hi @sbrannen , This issue is bit hard to reproduce in a new project when run on my development machine. I tested with the 5.2.8.RELEASE as well and observed the same issue but working with the 5.1.17.RELEASE. Below are the environment details which this issue is happening (strangely I didn't face this issue locally on macOS). OS
Tomcat
Also I tried removing
Thanks |
This is available in the latest 5.2.9 snapshot, feel free to give it a try and let me know whether it works for you now: |
@jhoeller, tested with 5.2.9.BUILD-SNAPSHOT and working as expected. Thanks! |
experiencing the same issue when using spring 5.2.12.RELEASE org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.transaction.annotation.AnnotationTransactionAttributeSource#0': BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager' defined in class path resource [DataAccess.class]: Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.transaction.config.internalTransactionAdvisor': Initialization of bean failed; nested exception is java.lang.StackOverflowError |
I'm seeing below error after upgrading the Spring framework from 5.1.13 to 5.2.7.
The text was updated successfully, but these errors were encountered: