apache / apache/incubator-seata
is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
在正式生产代码整合过程中出现:is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
————————————————————————————————————————
trationDelegate$BeanPostProcessorChecker : Bean 'com.pepper.configuration.transaction.TransactionConfiguration' of type [com.pepper.configuration.transaction.TransactionConfiguration$$EnhancerBySpringCGLIB$$289f21ef] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
ERROR 8950 --- [ restartedMain] c.a.f.c.ConfigFuture : config operation timeout,cost:5000 ms,op:GET,dataId:service.disableGlobalTransaction
com.pepper.configuration.transaction.TransactionConfiguration 为spring boot 自定义自动配置类,代码如下:
@Configuration
@ConditionalOnProperty(name = "enabled.globalTransaction", havingValue = "true")
@ConditionalOnClass(value={GlobalTransactionScanner.class})
public class TransactionConfiguration {
@Bean
public GlobalTransactionScanner globalTransactionScanner(Environment environment) {
return new GlobalTransactionScanner(environment.getProperty("spring.application.name","spring-boot-dubbo"),"my_test_tx_group");
}
}
————————————————————————————————————————
技术栈:spring boot 2.1.4 + dubbo 2.7 + jpa + fescar-server 0.4.2
fescar-server 采用解压后默认配置 只改了file.conf (service { default.grouplist = "10.10.100.137:8091" })然后将file.conf 和 registry.conf 复制到项目src/main/resources目录下
加有@GlobalTransactional的方法 有被自定义的两个AOP拦截代理过。
请问要如何解决,谢谢
Contributor guide
Research direction
Start with the custom TransactionConfiguration and its GlobalTransactionScanner bean, then inspect file.conf and registry.conf under src/main/resources alongside the startup warning and config operation timeout. Reproduce the Spring Boot 2.1.4 integration with the listed Dubbo, JPA, and fescar-server versions; done means identifying the cause and documenting a confirmed configuration or integration fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100