Skip to content
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

BUG REPORT: bean getting eagerly injected into a currently created BeanPostProcessor【RocketMQMessageListenerBeanPostProcessor】 #646

Open
chainray01 opened this issue Mar 18, 2024 · 2 comments

Comments

@chainray01
Copy link

The issue tracker is ONLY used for bug report and feature request.

Any question or RocketMQ proposal please use our mailing lists.

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?

  • What did you expect to see?

  • What did you see instead? 2024-03-18T15:00:42.421+08:00 WARN 98860 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration' of type [org.springframework.cloud.commons.config.CommonsConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [org.apache.rocketmq.spring.annotation.RocketMQMessageListenerBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies.

  1. Please tell us about your environment: spring-boot3.2.3 spring-cloud.version 2023.0.0 rocketmq-spring-boot-starter 2.3.0

  2. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

截屏2024-03-18 15 33 50

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

@ZhangWeiSep
Copy link

I encountered the same problem, has it been solved?

@wangkye
Copy link

wangkye commented Jun 28, 2024

I encountered the same problem as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants