Multiple trationDelegate$BeanPostProcessorChecker Warnings Arise When Using Spring Boot 3.2.0

[woosungkim0123]

Bug description
When attempting to run a Batch process in Spring Boot 3.2.0, multiple BeanPostProcessorChecker warnings are being logged.

Environment

• Spring Batch version: 5.1
• Java version: 17, 21
• Database used (if applicable): H2
• Additional environment details: Spring Boot 3.2.0

Steps to reproduce

1. Configure an application using Spring Boot 3.2.0, Spring Batch 5.1, and H2 database.
2. Run the application.
3. BeanPostProcessorChecker warnings appear in the log.

Expected behavior
The application should initialize and run without any BeanPostProcessorChecker warnings.

Minimal Complete Reproducible example
The warnings that are being displayed have been documented in the README of the demo project.
minimal example

[hpoettker]

The issue is caused by the automatic bean exposure of JobRegistryBeanPostProcessor that has been introduced with #4245.

If you don't need the job beans to be registered with the JobRegistry, or use your own custom mechanism, you can disable it with code like this in one of your configuration classes:

@Bean
public static BeanDefinitionRegistryPostProcessor jobRegistryBeanPostProcessorRemover() {
  return registry -> registry.removeBeanDefinition("jobRegistryBeanPostProcessor");
}

The warnings should then disappear.

[woosungkim0123]

thank you The issue has been resolved.

[pmsinclair]

For applications with: @EnableBatchProcessing(modular = true)
This can actually cause: DuplicateJobException
This is due to both of these trying to register the same jobs:

1. JobRegistryBeanPostProcessor
2. AutomaticJobRegistrarBeanPostProcessor

[woosungkim0123]

If this is what you intended or has been implemented in a new version, please feel free to close the issue.

[nightswimmings]

The issue indicated by the warning actually affects the app. I have a BeanPostProcessor that does not have any dependency and expects a certain bean autoconfigured and exposed by me in another section of the code, and as long as I don't add the removal mentioned by hpoettker, my custompostprocessor cannot find my custom bean

[fmbenhassine]

@woosungkim0123 Thank you for reporting this issue. This is not intentional, and those warning should be fixed. However, I think this issue is a duplicate of #4489, so I will close this one. Please follow the updates on #4489.

@pmsinclair That would be a bug! Please open a separate issue for that case. If you have a sample that reproduces the problem, please attach it in the issue.

@nightswimmings I don't see how the BPP added by Spring Batch could impact your custom BPP. If you think this is a side effect of #4245 , please open a separate issue with an example and we will address the problem.

Thank you all for your feedback on this!

[fmbenhassine]

I just wanted to mention that the mechanism of using a BPP to populate the registry is problematic and will be fixed in 5.2 (#4547). In the meantime, the workaround for warnings in 5.1.x is to remove the JobRegistryBeanPostProcessor bean as described in #4519 (comment). For those who need to populate the registry (when using the job operator for instance), a JobRegistrySmartInitializingSingleton will be available in 5.1.1 as a replacement of the BPP.