-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
PostProcessorRegistrationDelegate$BeanPostProcessorChecker.postProcessAfterInitialization WARNING after upgrade spring-framework-6.1.0 #4489
Comments
Duplicate of spring-projects/spring-data-jpa#3244 and spring-projects/spring-boot#38558. We're not quite sure where this comes from. |
@mp911de |
The sudden attention comes from the changed log level from The warnings are also logged with Java configuration (i.e. without XML) when the DefaultBatchConfiguration is used. The factory method for the |
when declare a beanPostProcessor in xxAutoConfiguration. there will be a warn log for the xxAutoConfiguration. and the bbpsInCreation is empty. so the log message would like "..injected into a currently created BeanPostProcessor [] ? Check the corresponding BeanPostProcessor declaration and its dependencies.", which looks a little strange. |
As far as I understand, the Edit: The code snippet from here, fixes that. |
@philippn There wasn't really a fix for these warnings in 5.1.1. The introduction of The proper fix for Java configuration is addressed in #4547, by replacing the BPP with the SIS in the default configuration. For XML configuration as reported in this issue, the now deprecated --<bean class="org.springframework.batch.core.configuration.support.JobRegistryBeanPostProcessor">
++<bean class="org.springframework.batch.core.configuration.support.JobRegistrySmartInitializingSingleton">
<property name="jobRegistry" ref="batch.job.registry" />
</bean> |
Please do a quick search on Github issues first, there might be already a duplicate issue for the one you are about to create.
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
Bug description
Environment
Steps to reproduce
Expected behavior
no warning
Minimal Complete Reproducible example
Please provide a failing test or a minimal complete verifiable example that reproduces the issue.
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
The text was updated successfully, but these errors were encountered: