Bean ... not elligible for getting processed by all BeanPostProcessors

[sebastianhaberey]

In what version(s) of Spring Integration are you seeing this issue?

5.3.13

Describe the bug

During startup of my Spring Integration application, the following three messages appear:

2022-11-15 08:21:40.518 INFO 85755 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'integrationChannelResolver' of type [org.springframework.integration.support.channel.BeanFactoryChannelResolver] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-11-15 08:21:40.521 INFO 85755 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'integrationDisposableAutoCreatedBeans' of type [org.springframework.integration.config.annotation.Disposables] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2022-11-15 08:21:40.538 INFO 85755 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.integration.config.IntegrationManagementConfiguration' of type [org.springframework.integration.config.IntegrationManagementConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

Expected behavior

All beans are created without warning.

Details

I undestand this is due to cyclic dependencies between beans. I get that these are informational messages, and that the beans in question likely don't need to be post-processed, but they are still bothersome.

Is there anything I can do in my application to avoid these messages? Or if not, could this be fixed in Spring Integration?

[artembilan]

Let's see how it works for you with really the latest 5.5.15 version: https://spring.io/projects/spring-integration#learn!

There is no that org.springframework.integration.config.annotation.Disposables any more.

It would be also great to see some simple project from you to be able to reproduce on our side and determine what is wrong.

[artembilan]

OK. I found the problem with IntegrationManagementConfiguration.
It does produce an IntegrationManagementConfigurer which is a BeanPostProcessor.
According to Spring recommendation this kind of infrastructure beans must be declared as static.
Due to an implements ImportAware, EnvironmentAware nature of the IntegrationManagementConfiguration, we cannot use static @Bean method.
But since the IntegrationManagementConfiguration is not involved in any bean post-processing, it is safe to follow recommendation and mark it as a @Role(BeanDefinition.ROLE_INFRASTRUCTURE).

Looking to that BeanFactoryChannelResolver next...

[sebastianhaberey]

Yes, that's what I saw during debugging too:

	Bean [type]	depending on BeanPostProcessor [type]
1	integrationChannelResolver [BeanFactoryChannelResolver]	internalMessagingAnnotationPostProcessor [BeanPostProcessor]
2	integrationDisposableAutoCreatedBeans [Disposables]	internalMessagingAnnotationPostProcessor [BeanPostProcessor]
3	IntegrationManagementConfiguration [IntegrationManagementConfiguration]	integrationManagementConfigurer [BeanPostProcessor]