apache / apache/incubator-seata
org.apache.seata.config.exception.ConfigNotFoundException: service.vgroupMapping.default_tx_group configuration item is required
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
我是使用docker 部署 nacos 和 seata 然後已經確認seata 已經連上nacos 配置的seataServer.properties 但是我是用客戶端spring boot 連nacos seata 的時候一直報 ConfigNotFoundException: service.vgroupMapping.default_tx_group configuration item is required。 想求大佬幫忙看下什麽問題
### **Docker Images**
> - apache/seata-server:2.3.0.jdk21
> - nacos/nacos-server:latest
### **Spring Boot Dependencies**
> - org.apache.seata - seata-spring-boot-starter - 2.3.0
> - com.alibaba.cloud - spring-cloud-alibaba-dependencies - 2023.0.3.2
### **Docker run nacos and seata**
```
docker run -d --name nacos
-p 8848:8848 -p 8080:8080
--network seata-net
-v /c/Users/admin/Desktop/microservice-server/nacos/data:/home/nacos/data
-v /c/Users/admin/Desktop/microservice-server/nacos/logs:/home/nacos/logs
-e MODE=standalone
-e NACOS_AUTH_ENABLE=true
-e NACOS_AUTH_TOKEN=test
-e NACOS_AUTH_IDENTITY_KEY=test
-e NACOS_AUTH_IDENTITY_VALUE=seata
nacos/nacos-server:latest
docker run -d --name seata-server
-p 7091:7091 -p 8091:8091
--network seata-net
-e SEATA_IP=127.0.0.1
-v /c/Users/admin/Desktop/microservice-server/seata/application.yml:/seata-server/resources/application.yml
-v /c/Users/admin/Desktop/microservice-server/libs/mysql-connector-j-8.4.0.jar:/seata-server/libs/mysql-connector-j-8.4.0.jar
apache/seata-server:2.3.0.jdk21
```
### **Nacos 配置的 seataServer.properties**

```
transport.type=TCP
transport.server=NIO
transport.heartbeat=true
transport.enableTmClientBatchSendRequest=false
transport.enableRmClientBatchSendRequest=true
transport.enableTcServerBatchSendResponse=false
transport.rpcRmRequestTimeout=30000
transport.rpcTmRequestTimeout=30000
transport.rpcTcRequestTimeout=30000
transport.threadFactory.bossThreadPrefix=NettyBoss
transport.threadFactory.workerThreadPrefix=NettyServerNIOWorker
transport.threadFactory.serverExecutorThreadPrefix=NettyServerBizHandler
transport.threadFactory.shareBossWorker=false
transport.threadFactory.clientSelectorThreadPrefix=NettyClientSelector
transport.threadFactory.clientSelectorThreadSize=1
transport.threadFactory.clientWorkerThreadPrefix=NettyClientWorkerThread
transport.threadFactory.bossThreadSize=1
transport.threadFactory.workerThreadSize=default
transport.shutdown.wait=3
transport.serialization=seata
transport.compressor=none
#Transaction routing rules configuration, only for the client
service.vgroupMapping.default_tx_group=default
client.metadataMaxAgeMs=30000
#Transaction rule configuration, only for the client
client.rm.asyncCommitBufferLimit=10000
client.rm.lock.retryInterval=10
client.rm.lock.retryTimes=30
client.rm.lock.retryPolicyBranchRollbackOnConflict=true
client.rm.reportRetryCount=5
client.rm.tableMetaCheckEnable=true
client.rm.tableMetaCheckerInterval=60000
client.rm.sqlParserType=druid
client.rm.reportSuccessEnable=false
client.rm.sagaBranchRegisterEnable=false
client.rm.sagaJsonParser=fastjson
client.rm.tccActionInterceptorOrder=-2147482648
client.rm.sqlParserType=druid
client.tm.commitRetryCount=5
client.tm.rollbackRetryCount=5
client.tm.defaultGlobalTransactionTimeout=60000
client.tm.degradeCheck=false
client.tm.degradeCheckAllowTimes=10
client.tm.degradeCheckPeriod=2000
client.tm.interceptorOrder=-2147482648
client.undo.dataValidation=true
client.undo.logSerialization=jackson
client.undo.onlyCareUpdateColumns=true
server.undo.logSaveDays=7
server.undo.logDeletePeriod=86400000
client.undo.logTable=undo_log
client.undo.compress.enable=true
client.undo.compress.type=zip
client.undo.compress.threshold=64k
#For TCC transaction mode
tcc.fence.logTableName=tcc_fence_log
tcc.fence.cleanPeriod=1h
# You can choose from the following options: fastjson, jackson, gson
tcc.contextJsonParserType=fastjson
#Log rule configuration, for client and server
log.exceptionRate=100
#Transaction storage configuration, only for the server. The file, db, and redis configuration values are optional.
store.mode=db
store.lock.mode=db
store.session.mode=db
#Used for password encryption
store.publicKey=
#These configurations are required if the `store mode` is `db`. If `store.mode,store.lock.mode,store.session.mode` are not equal to `db`, you can remove the configuration block.
store.db.datasource=druid
store.db.dbType=mysql
store.db.driverClassName=com.mysql.cj.jdbc.Driver
store.db.url=jdbc:mysql://host.docker.internal:3306/seata?useUnicode=true&characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true&useSSL=false
store.db.user=root
store.db.password=test
store.db.minConn=5
store.db.maxConn=30
store.db.globalTable=global_table
store.db.branchTable=branch_table
store.db.distributedLockTable=distributed_lock
store.db.vgroupTable=vgroup_table
store.db.queryLimit=100
store.db.lockTable=lock_table
store.db.maxWait=5000
#Transaction rule configuration, only for the server
server.recovery.committingRetryPeriod=1000
server.recovery.asynCommittingRetryPeriod=1000
server.recovery.rollbackingRetryPeriod=1000
server.recovery.timeoutRetryPeriod=1000
server.maxCommitRetryTimeout=-1
server.maxRollbackRetryTimeout=-1
server.rollbackRetryTimeoutUnlockEnable=false
server.distributedLockExpireTime=10000
server.session.branchAsyncQueueSize=5000
server.session.enableBranchAsyncRemove=false
server.enableParallelRequestHandle=true
server.enableParallelHandleBranch=false
server.applicationDataLimit=64000
server.applicationDataLimitCheck=false
#Metrics configuration, only for the server
metrics.enabled=true
metrics.registryType=compact
metrics.exporterList=prometheus
metrics.exporterPrometheusPort=9898
```
### **Seata application.yml**
```
server:
port: 7091
spring:
application:
name: seata-server
logging:
config: classpath:logback-spring.xml
file:
path: ${log.home:${user.home}/logs/seata}
extend:
logstash-appender:
destination: 127.0.0.1:4560
kafka-appender:
bootstrap-servers: 127.0.0.1:9092
topic: logback_to_logstash
console:
user:
username: seata
password: seata
seata:
config:
# support: nacos, consul, apollo, zk, etcd3
type: nacos
nacos:
server-addr: 127.0.0.1:8848
group: SEATA_GROUP
namespace: seata
username: nacos
password: nacos
data-id: seataServer.properties
registry:
# support: nacos, eureka, redis, zk, consul, etcd3, sofa
type: nacos
nacos:
application: seata-server
server-addr: 127.0.0.1:8848
cluster: default
group: SEATA_GROUP
namespace: seata
username: nacos
password: nacos
store:
# support: file 、 db 、 redis 、 raft
mode: file
security:
secretKey: SeataSecretKey0c382ef121d778043159209298fd40bf3850a017
tokenValidityInMilliseconds: 1800000
csrf-ignore-urls: /metadata/v1/**
ignore:
urls: /,/**/*.css,/**/*.js,/**/*.html,/**/*.map,/**/*.svg,/**/*.png,/**/*.jpeg,/**/*.ico,/api/v1/auth/login,/version.json,/health,/error,/vgroup/v1/**
```
### **Seata server 已經注冊到Nacos Service List**

### **Seata server 已經連接到seataServer.properties**

### **Spring boot application.yml**
```
app-info:
name: cliqbase_auth
spring:
application:
name: auth-service
cloud:
nacos:
discovery:
server-addr: nacos:8848
username: nacos
password: nacos
ip: 127.0.0.1
profiles:
active: dev
datasource:
url: jdbc:mysql://${MYSQL_HOST:localhost}:3306/${app-info.name}
username: root
password: test
driver-class-name: com.mysql.cj.jdbc.Driver
jpa:
hibernate:
ddl-auto: none
show-sql: true
properties:
hibernate:
dialect: org.hibernate.dialect.MySQLDialect
flyway:
enabled: true
baseline-on-migrate: true
out-of-order: true
locations: classpath:db/migration
seata:
enabled: true
tx-service-group: default_tx_group
registry:
type: nacos
nacos:
application: seata-server
server-addr: nacos:8848
group: SEATA_GROUP
namespace: seata
username: nacos
password: nacos
config:
type: nacos
nacos:
server-addr: nacos:8848
namespace: seata
group: SEATA_GROUP
username: nacos
password: nacos
data-id: seataServer.properties
server:
port: 8081
```
最後還是報了這個error
```
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v3.4.5)
2025-05-20T16:19:21.584+08:00 INFO 22556 --- [auth-service] [ main] c.t.c.a.AuthServiceApplication : Starting AuthServiceApplication using Java 21.0.6 with PID 22556 (C:\Users\admin\idea-projects\cliqbase\auth-service\target\classes started by admin in C:\Users\admin\idea-projects\cliqbase)
2025-05-20T16:19:21.586+08:00 INFO 22556 --- [auth-service] [ main] c.t.c.a.AuthServiceApplication : The following 1 profile is active: "dev"
2025-05-20T16:19:23.210+08:00 INFO 22556 --- [auth-service] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2025-05-20T16:19:23.309+08:00 INFO 22556 --- [auth-service] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 82 ms. Found 1 JPA repository interface.
2025-05-20T16:19:23.607+08:00 INFO 22556 --- [auth-service] [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=36a8a487-3479-3efc-b441-70580609499d
2025-05-20T16:19:23.721+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.apache.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration' of type [org.apache.seata.spring.boot.autoconfigure.SeataCoreAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.724+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'springApplicationContextProvider' of type [org.apache.seata.spring.boot.autoconfigure.provider.SpringApplicationContextProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.725+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.apache.seata.spring.boot.autoconfigure.SeataAutoConfiguration' of type [org.apache.seata.spring.boot.autoconfigure.SeataAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.831+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'failureHandler' of type [org.apache.seata.tm.api.DefaultFailureHandlerImpl] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.875+08:00 WARN 22556 --- [auth-service] [ 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/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.884+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.885+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'loadBalancerClientsDefaultsMappingsProvider' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration$$Lambda/0x0000024801410a98] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.887+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'defaultsBindHandlerAdvisor' of type [org.springframework.cloud.commons.config.DefaultsBindHandlerAdvisor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.894+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.897+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'stringOrNumberMigrationVersionConverter' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$StringOrNumberToMigrationVersionConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.903+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'springCloudAlibabaConfiguration' of type [org.apache.seata.spring.boot.autoconfigure.properties.SpringCloudAlibabaConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.910+08:00 WARN 22556 --- [auth-service] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'seataProperties' of type [org.apache.seata.spring.boot.autoconfigure.properties.SeataProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-05-20T16:19:23.915+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.s.b.a.SeataAutoConfiguration : Automatically configure Seata
2025-05-20T16:19:23.962+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.spring.annotation.ScannerChecker
2025-05-20T16:19:24.065+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Ignore load compatible class io.seata.config.ExtConfigurationProvider, because is not assignable from origin type org.apache.seata.config.ExtConfigurationProvider
2025-05-20T16:19:24.229+08:00 INFO 22556 --- [auth-service] [ main] o.a.seata.config.ConfigurationFactory : load Configuration from :FileConfiguration$$EnhancerByCGLIB$$9e6bf6fd
2025-05-20T16:19:24.234+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.config.ConfigurationProvider
2025-05-20T16:19:24.244+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.config.nacos.NacosConfiguration : Nacos check auth with userName/password.
2025-05-20T16:19:24.407+08:00 INFO 22556 --- [auth-service] [ main] c.a.n.p.a.s.c.ClientAuthPluginManager : [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success.
2025-05-20T16:19:24.407+08:00 INFO 22556 --- [auth-service] [ main] c.a.n.p.a.s.c.ClientAuthPluginManager : [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success.
2025-05-20T16:19:28.849+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.integration.tx.api.remoting.RemotingParser
2025-05-20T16:19:28.850+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.s.a.GlobalTransactionScanner : Initializing Global Transaction Clients ...
2025-05-20T16:19:34.189+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.core.auth.AuthSigner
2025-05-20T16:19:35.086+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.c.rpc.netty.NettyClientBootstrap : NettyClientBootstrap has started
2025-05-20T16:19:35.522+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.d.registry.RegistryFactory : use registry center type: nacos
2025-05-20T16:19:35.537+08:00 INFO 22556 --- [auth-service] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.discovery.registry.RegistryProvider
2025-05-20T16:19:35.543+08:00 INFO 22556 --- [auth-service] [ main] o.a.s.d.r.n.NacosRegistryServiceImpl : Nacos check auth with userName/password.
2025-05-20T16:19:35.985+08:00 ERROR 22556 --- [auth-service] [ main] o.a.s.c.r.n.NettyClientChannelManager : Failed to get available servers: service.vgroupMapping.default_tx_group configuration item is required
org.apache.seata.config.exception.ConfigNotFoundException: service.vgroupMapping.default_tx_group configuration item is required
at org.apache.seata.discovery.registry.nacos.NacosRegistryServiceImpl.lookup(NacosRegistryServiceImpl.java:154) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:301) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.doReconnect(NettyClientChannelManager.java:187) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.initReconnect(NettyClientChannelManager.java:176) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.initConnection(TmNettyRemotingClient.java:293) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:193) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:247) ~[seata-all-2.3.0.jar:2.3.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:495) ~[seata-all-2.3.0.jar:2.3.0]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1865) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1814) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:607) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:371) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:337) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:207) ~[spring-beans-6.2.6.jar:6.2.6]
at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:265) ~[spring-context-6.2.6.jar:6.2.6]
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:808) ~[spring-context-6.2.6.jar:6.2.6]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:611) ~[spring-context-6.2.6.jar:6.2.6]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.4.5.jar:3.4.5]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:753) ~[spring-boot-3.4.5.jar:3.4.5]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:439) ~[spring-boot-3.4.5.jar:3.4.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:318) ~[spring-boot-3.4.5.jar:3.4.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1362) ~[spring-boot-3.4.5.jar:3.4.5]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1351) ~[spring-boot-3.4.5.jar:3.4.5]
at com.techcasys.cliqbase.auth_service.AuthServiceApplication.main(AuthServiceApplication.java:8) ~[classes/:na]
2025-05-20T16:19:35.988+08:00 WARN 22556 --- [auth-service] [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'globalTransactionScanner' defined in class path resource [org/apache/seata/spring/boot/autoconfigure/SeataAutoConfiguration.class]: Failed to get available servers
2025-05-20T16:19:36.006+08:00 INFO 22556 --- [auth-service] [ main] .s.b.a.l.ConditionEvaluationReportLogger :
```
我一直嘗試了很多方法 try and error 還是不能 希望大佬們幫個忙 我快要絕望了
Contributor guide
Research direction
Start by comparing the client application.yml, the server application.yml, and the Nacos seataServer.properties values, then review the Spring Boot startup log around ConfigNotFoundException. Reproduce the client startup with the listed Docker and dependency versions; done means the default_tx_group configuration is read and the client starts without this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, spring-boot
- Domain
- backend, devops, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100