chainray01 opened a new issue, #646:
URL: https://github.com/apache/rocketmq-spring/issues/646

   The issue tracker is **ONLY** used for bug report and feature request. 
   
   Any question or RocketMQ proposal please use our [mailing 
lists](http://rocketmq.apache.org/about/contact/).
   
   **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.
   `
   2. Please tell us about your environment: spring-boot3.2.3  
spring-cloud.version 2023.0.0 rocketmq-spring-boot-starter 2.3.0
   
   3. Other information (e.g. detailed explanation, logs, related issues, 
suggestions how to fix, etc):
   <img width="1401" alt="截屏2024-03-18 15 33 50" 
src="https://github.com/apache/rocketmq-spring/assets/5676095/61cd803a-ed8c-42a2-93c3-7562ac8da535";>
   
   
   **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?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to