apache / apache/incubator-seata-samples
io.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : io.seata.sqlparser.druid.SQLOperateRecognizerHolder
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
使用eureka注册中心seata1.4.2,Springboot版本2.5.12,SpringCloud版本 2020.0.4,
druid连接池,阿里云polardb-o数据库
事务还没进去报这个错
io.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : io.seata.sqlparser.druid.SQLOperateRecognizerHolder
--server
registry {
# file 、nacos 、eureka、redis、zk、consul、etcd3、sofa
type = "eureka"
eureka {
serviceUrl = "http://10.0.0.66:8761/eureka/"
application = "seata-server-oa"
weight = "1"
}
}
--client
seata.application-id=${spring.application.name}
seata.tx-service-group=default_tx_group
seata.service.vgroup-mapping.default_tx_group=seata-server-oa
seata.enable-auto-data-source-proxy=true
seata.data-source-proxy-mode=AT
seata.use-jdk-proxy=false
seata.service.disable-global-transaction=false
seata.registry.type=eureka
seata.registry.eureka.application=${spring.application.name}
seata.registry.eureka.service-url=http://10.0.0.66:8761/eureka/
seata.registry.eureka.weight=1
哪位大神能帮我看看啊
Contributor guide
Research direction
Start by reproducing the reported startup or transaction failure with Seata 1.4.2, Spring Boot 2.5.12, Eureka, the Druid connection pool, and PolarDB-O. Trace the EnhancedServiceNotFoundException for io.seata.sqlparser.druid.SQLOperateRecognizerHolder and inspect the registry and data-source proxy settings; done means the service provider is resolved and the transaction begins without this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100