MessagingAnnotationBeanPostProcessor or ProxyTransactionManagementConfiguration BeanPostProcessor error about spring-boot

[scottfrederick]

This appears to be a duplicate of spring-projects/spring-framework#32882. Please try the workarounds suggested in that issue, or build against the latest Spring Framework 6.1 snapshots to verify the fix.

If the workarounds or the Framework fix don't solve the problem, please provide a complete minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it and attaching it to this issue.

[hoanvh]

I got the same issue when bumping SB from 3.2.5 to 3.3.0.
In my case:

• EnableMethodSecurity ~> ASPECTJ mode
• EnableTransactionManagement ~> PROXY mode (default).
• EnableCaching ~> PROXY mode (default).

After switching between Proxy & AspectJ, I found the same phenomenon: When there is a mix of Proxy & AspectJ, there will be an exception like (thrown in AbstractAspectJAdvice):

IllegalStateException: Expecting to find X arguments to bind by name in advice, but actually found Y arguments.

Above workaround does not work for me, even after I use AspectJ mode for each of EnableMethodSecurity, EnableTransactionManagement and EnableCaching. Another exception will be thrown with built-in components in SB:

BeanCreationException: Error creating bean with name 'healthEndpointGroupsBeanPostProcessor' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: BeanPostProcessor before instantiation of bean failed
...
IllegalStateException: Expecting to find 3 arguments to bind by name in advice, but actually found 2 arguments.

[bclozel]

@hoanvh thanks for letting us know. Have you tried upgrading your application to the latest Spring Framework SNAPSHOTs to verify the fix?

[hoanvh]

@bclozel yes, I've just found that comment, and I confirm that framework 6.1.9-SNAPSHOT works for me.
Thank a lot.

[bclozel]

Thanks for letting us know. I'll close this issue for now. @willome if Spring Framework SNAPSHOTs don't fix the problem, please create a new issue here with a sample application that reproduces the problem.

[willome]

I confirm that upgrading spring-framework to 6.1.9-SNAPSHOT was the only way to fix the problem. Let's keep this issue closed for the moment. Thank you.