RockteMQ-AI commented on issue #738: URL: https://github.com/apache/rocketmq-spring/issues/738#issuecomment-5192833216
**Issue Evaluation** Category: `question` The `not eligible for auto-proxying` warning typically occurs when a bean is accessed before all BeanPostProcessors have been initialized. In RocketMQ Spring, this can happen when the listener container registers and starts consuming during `afterPropertiesSet()`, which may trigger early bean initialization. **This is usually harmless** — it means the specific bean won't receive certain AOP proxies (e.g., `@Transactional`, `@Async`). If your listener class uses AOP annotations and they are not being applied, this is the likely cause. **Workaround:** Defer the listener container startup to a `SmartLifecycle` phase or use `@Lazy` on the listener bean reference. --- *Automated evaluation by RockteMQ-AI* -- 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]
