You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@seata.apache.org by "GCwithH2O (via GitHub)" <gi...@apache.org> on 2025/06/06 02:49:53 UTC
[I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
GCwithH2O opened a new issue, #7416:
URL: https://github.com/apache/incubator-seata/issues/7416
### Check Ahead
- [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.
### Ⅰ. Issue Description
使用docker部署seata，cloud alibaba从2023.0.1.2升级到2023.0.3.3，涉及到几个服务的升级如下：
```
spring-cloud-alibaba-dependencies : 2023.0.1.2 ->2023.0.3.3
seata docker image : 最早尝试：2.0.0-slim -> 2.1.0
后来尝试：2.0.2-slim -> 2.4.0
nacos docker image : v2.3.2-slim -> 2.4.2
```
几个主要jar版本如下：
```
spring-cloud-dependencies : 2023.0.3
spring-cloud-alibaba-dependencies : 2023.0.3.3
spring-boot-starter-parent : 3.2.9
```
java版本： `21`
docker容器启动成功，seata也注册到了nacos，可以在服务列表中找到：
| 服务名 | 分组名称 | 集群数目 | 实例数 | 健康实例数 | 触发保护阈值 |
| :----------- | :---------- | :------- | :----- | :--------- | :----------- |
| seata-server | SEATA_GROUP | 1 | 1 | 1 | false |
Nacos 配置的 seata-server.properties：
| Data Id | Group | 格式 | 归属应用 |
| :------ | :---------------------- | :---------- | :--------- |
| seata-server.properties | SEATA_GROUP | Properties | |
内容：
``` properties
#For details about configuration items, see https://seata.io/zh-cn/docs/user/configurations.html
#Transport configuration, for client and server
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_group123=default
#If you use a registry, you can ignore it
service.default.grouplist=192.168.200.208:8091
service.enableDegrade=false
service.disableGlobalTransaction=false
#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.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
#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
#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://127.0.0.1:3306/seata?useUnicode=true&rewriteBatchedStatements=true
store.db.user=root
store.db.password=root
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.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.rollbackFailedUnlockEnable=false
server.distributedLockExpireTime=10000
server.xaerNotaRetryTimeout=60000
server.session.branchAsyncQueueSize=5000
server.session.enableBranchAsyncRemove=false
server.enableParallelRequestHandle=false
#Metrics configuration, only for the server
metrics.enabled=false
metrics.registryType=compact
metrics.exporterList=prometheus
metrics.exporterPrometheusPort=9898
```
业务服务使用`spring-cloud-starter-bootstrap`加载启动配置，
bootstrap.yml内容：
``` yaml
spring:
application:
name: authorization-server
profiles:
active: dev
main:
allow-bean-definition-overriding: true
cloud:
compatibility-verifier:
enabled: false
nacos:
username: nacos
password: nacos
discovery:
ip: 192.168.xxx.xxx
config:
server-addr: 192.168.200.208:8848
file-extension: yml
shared-configs:
- data-id: shared-datasource-mysql.yml
group: DEFAULT_GROUP
- data-id: shared-feign.yml
group: DEFAULT_GROUP
- data-id: shared-redis.yml
group: DEFAULT_GROUP
- data-id: shared-seata.yml
group: DEFAULT_GROUP
```
shared-seata.yml内容：
``` yaml
seata:
tx-service-group: default_tx_group123
enabled: true
registry:
type: nacos
nacos:
application: seata-server
server-addr: ${spring.cloud.nacos.config.server-addr}
group : SEATA_GROUP
namespace:
username: nacos
password: nacos
cluster: default
config:
type: nacos
nacos:
server-addr: ${spring.cloud.nacos.config.server-addr}
namespace:
group : SEATA_GROUP
username: nacos
password: nacos
data-id: seata-server.properties
service:
disableGlobalTransaction: false
vgroupMapping:
default_tx_group123: default
```
seata-server的启动配置文件application.yml：
``` yaml
server:
port: 7091
spring:
application:
name: seata-server
logging:
config: classpath:logback-spring.xml
file:
path: ${log.home:${user.home}/logs/seata}
console:
user:
username: seata
password: seata
seata:
config:
# support: nacos, consul, apollo, zk, etcd3
type: nacos
nacos:
server-addr: 192.168.200.208:8848
group : SEATA_GROUP
namespace:
dataId: seata-server.properties
username: nacos
password: nacos
registry:
# support: nacos, eureka, redis, zk, consul, etcd3, sofa
type: nacos
nacos:
application: seata-server
server-addr: ${seata.config.nacos.server-addr}
namespace:
group : SEATA_GROUP
username: nacos
password: nacos
cluster: default
store:
# support: file 、 db 、 redis 、 raft
mode: file
# server:
# service-port: 8091 #If not configured, the default is '${server.port} + 1000'
security:
secretKey: SeataSecretKey0c382ef121d778043159209298fd40bf3850a017
tokenValidityInMilliseconds: 1800000
ignore:
urls: /,/**/*.css,/**/*.js,/**/*.html,/**/*.map,/**/*.svg,/**/*.png,/**/*.jpeg,/**/*.ico,/api/v1/auth/login,/version.json,/health,/error
```
### Ⅱ. Describe what happened
启动业务服务启动日志报错：
```
2025-06-06T10:45:12.516+08:00 INFO 31280 --- [authorization-server] [ main] c.a.nacos.client.logging.NacosLogging : Nacos Logging Adapter Builder: com.alibaba.nacos.logger.adapter.logback12.LogbackNacosLoggingAdapterBuilder
2025-06-06T10:45:12.527+08:00 INFO 31280 --- [authorization-server] [ main] c.a.nacos.client.logging.NacosLogging : Nacos Logging Adapter Builder: com.alibaba.nacos.logger.adapter.logback14.LogbackNacosLoggingAdapterBuilder
2025-06-06T10:45:12.529+08:00 INFO 31280 --- [authorization-server] [ main] c.a.nacos.client.logging.NacosLogging : Nacos Logging Adapter: com.alibaba.nacos.logger.adapter.logback14.LogbackNacosLoggingAdapter match ch.qos.logback.classic.Logger success.
2025-06-06T10:45:12.542+08:00 INFO 31280 --- [authorization-server] [ main] c.a.nacos.client.logging.NacosLogging : Nacos Logging Adapter Builder: com.alibaba.nacos.logger.adapter.log4j2.Log4j2NacosLoggingAdapterBuilder
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v3.2.9)
2025-06-06T10:45:14.484+08:00 INFO 31280 --- [authorization-server] [ main] c.h.kome.AuthorizationServerApplication : The following 1 profile is active: "dev"
2025-06-06T10:45:16.012+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2025-06-06T10:45:16.014+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data MongoDB repositories in DEFAULT mode.
2025-06-06T10:45:16.068+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 48 ms. Found 0 MongoDB repository interfaces.
2025-06-06T10:45:16.088+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
2025-06-06T10:45:16.090+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2025-06-06T10:45:16.132+08:00 INFO 31280 --- [authorization-server] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 30 ms. Found 0 Redis repository interfaces.
2025-06-06T10:45:16.627+08:00 INFO 31280 --- [authorization-server] [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=6a771ca8-87b1-3574-b15b-748cc247737f
2025-06-06T10:45:16.768+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.769+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.769+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.845+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor []? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.851+08:00 WARN 31280 --- [authorization-server] [ 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 [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.856+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.858+08:00 WARN 31280 --- [authorization-server] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'loadBalancerClientsDefaultsMappingsProvider' of type [org.springframework.cloud.client.loadbalancer.LoadBalancerDefaultMappingsProviderAutoConfiguration$$Lambda/0x00000237014ccf00] 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 [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.859+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.866+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.869+08:00 WARN 31280 --- [authorization-server] [ 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 into a currently created BeanPostProcessor [globalTransactionScanner]? Check the corresponding BeanPostProcessor declaration and its dependencies.
2025-06-06T10:45:16.875+08:00 INFO 31280 --- [authorization-server] [ main] o.a.s.s.b.a.SeataAutoConfiguration : Automatically configure Seata
2025-06-06T10:45:16.916+08:00 INFO 31280 --- [authorization-server] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.spring.annotation.ScannerChecker
2025-06-06T10:45:16.993+08:00 INFO 31280 --- [authorization-server] [ main] ServiceLoader$InnerEnhancedServiceLoader : Ignore load compatible class io.seata.config.ExtConfigurationProvider, because is not assignable from origin type org.apache.seata.config.ExtConfigurationProvider
2025-06-06T10:45:17.006+08:00 INFO 31280 --- [authorization-server] [ main] o.a.seata.config.ConfigurationFactory : load Configuration from :Spring Configuration
2025-06-06T10:45:17.044+08:00 INFO 31280 --- [authorization-server] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.integration.tx.api.remoting.RemotingParser
2025-06-06T10:45:17.045+08:00 INFO 31280 --- [authorization-server] [ main] o.a.s.s.a.GlobalTransactionScanner : Initializing Global Transaction Clients ...
2025-06-06T10:45:17.148+08:00 INFO 31280 --- [authorization-server] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.core.auth.AuthSigner
2025-06-06T10:45:17.164+08:00 INFO 31280 --- [authorization-server] [ main] o.a.s.c.rpc.netty.NettyClientBootstrap : NettyClientBootstrap has started
2025-06-06T10:45:17.173+08:00 INFO 31280 --- [authorization-server] [ main] o.a.s.d.registry.RegistryFactory : use registry center type: file
2025-06-06T10:45:17.180+08:00 INFO 31280 --- [authorization-server] [ main] ServiceLoader$InnerEnhancedServiceLoader : Load compatible class io.seata.discovery.registry.RegistryProvider
2025-06-06T10:45:17.192+08:00 ERROR 31280 --- [authorization-server] [ 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.FileRegistryServiceImpl.lookup(FileRegistryServiceImpl.java:85) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.getAvailServerList(NettyClientChannelManager.java:299) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.doReconnect(NettyClientChannelManager.java:187) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.initReconnect(NettyClientChannelManager.java:176) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.initConnection(TmNettyRemotingClient.java:291) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:191) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:232) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:480) ~[seata-all-2.1.0.jar:2.1.0]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1853) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1802) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:600) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:522) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:337) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:335) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:205) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:265) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:806) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:609) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:456) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:335) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1363) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1352) ~[spring-boot-3.2.9.jar:3.2.9]
at com.hchy.kome.AuthorizationServerApplication.main(AuthorizationServerApplication.java:28) ~[classes/:na]
2025-06-06T10:45:17.198+08:00 WARN 31280 --- [authorization-server] [ 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-06-06T10:45:17.216+08:00 INFO 31280 --- [authorization-server] [ main] .s.b.a.l.ConditionEvaluationReportLogger :
Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
2025-06-06T10:45:17.249+08:00 ERROR 31280 --- [authorization-server] [ main] o.s.boot.SpringApplication : Application run failed
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
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1806) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:600) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:522) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:337) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:335) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:205) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:265) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:806) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:609) ~[spring-context-6.1.12.jar:6.1.12]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:146) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:754) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:456) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:335) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1363) ~[spring-boot-3.2.9.jar:3.2.9]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1352) ~[spring-boot-3.2.9.jar:3.2.9]
at com.hchy.kome.AuthorizationServerApplication.main(AuthorizationServerApplication.java:28) ~[classes/:na]
Caused by: org.apache.seata.common.exception.FrameworkException: Failed to get available servers
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.throwFailFastException(NettyClientChannelManager.java:336) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.doReconnect(NettyClientChannelManager.java:190) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.NettyClientChannelManager.initReconnect(NettyClientChannelManager.java:176) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.initConnection(TmNettyRemotingClient.java:291) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.core.rpc.netty.TmNettyRemotingClient.init(TmNettyRemotingClient.java:191) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.tm.TMClient.init(TMClient.java:47) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.initClient(GlobalTransactionScanner.java:232) ~[seata-all-2.1.0.jar:2.1.0]
at org.apache.seata.spring.annotation.GlobalTransactionScanner.afterPropertiesSet(GlobalTransactionScanner.java:480) ~[seata-all-2.1.0.jar:2.1.0]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1853) ~[spring-beans-6.1.12.jar:6.1.12]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1802) ~[spring-beans-6.1.12.jar:6.1.12]
... 16 common frames omitted
2025-06-06T10:45:17.251+08:00 WARN 31280 --- [authorization-server] [ Thread-2] c.a.n.common.executor.ThreadPoolManager : [ThreadPoolManager] Start destroying ThreadPool
2025-06-06T10:45:17.252+08:00 WARN 31280 --- [authorization-server] [ Thread-2] c.a.n.common.executor.ThreadPoolManager : [ThreadPoolManager] Destruction of the end
```
配置文件中的default_tx_group123后面这个123是后来为了调试加的，没加的时候也报相同的错
### Ⅲ. Describe what you expected to happen
_No response_
### Ⅳ. How to reproduce it (as minimally and precisely as possible)
_No response_
### Ⅴ. Anything else we need to know?
_No response_
### Ⅵ. Environment
_No response_
--
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: notifications-unsubscribe@seata.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "funky-eyes (via GitHub)" <gi...@apache.org>.
funky-eyes commented on issue #7416:
URL: https://github.com/apache/incubator-seata/issues/7416#issuecomment-2947932411
由于你一直没有配置事务分组，1.5.2以后得默认事务分组为default_tx_group。所以你需要在你的配置中心中配置这个事务分组信息
Since you haven't configured the transaction group, the default transaction group after version 1.5.2 is default_tx_group. Therefore, you need to configure this transaction group information in your configuration center.
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "GCwithH2O (via GitHub)" <gi...@apache.org>.
GCwithH2O commented on issue #7416:
URL: https://github.com/apache/incubator-seata/issues/7416#issuecomment-2948227585
> 
>
> nacos上有事务分组这个远程配置文件吗
> 由于你一直没有配置事务分组，1.5.2以后得默认事务分组为default_tx_group。所以你需要在你的配置中心中配置这个事务分组信息 Since you haven't configured the transaction group, the default transaction group after version 1.5.2 is default_tx_group. Therefore, you need to configure this transaction group information in your configuration center.
是指的这块配置吗？
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "GCwithH2O (via GitHub)" <gi...@apache.org>.
GCwithH2O closed issue #7416: cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败
URL: https://github.com/apache/incubator-seata/issues/7416
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "xucq07 (via GitHub)" <gi...@apache.org>.
xucq07 commented on issue #7416:
URL: https://github.com/apache/incubator-seata/issues/7416#issuecomment-2947918831
nacos上有事务分组名这个远程配置文件吗
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "GCwithH2O (via GitHub)" <gi...@apache.org>.
GCwithH2O commented on issue #7416:
URL: https://github.com/apache/incubator-seata/issues/7416#issuecomment-2948285993
已解决：bootstrap方式启动已被弃用并默认禁用，改写成spring.config.import方式即可
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org
Re: [I] cloud alibaba从2023.0.1.2升级到2023.0.3.3后seata启动失败 [incubator-seata]
Posted by "lowjiahie (via GitHub)" <gi...@apache.org>.
lowjiahie commented on issue #7416:
URL: https://github.com/apache/incubator-seata/issues/7416#issuecomment-3048313421
> 已解决：bootstrap方式启动已被弃用并默认禁用，shared-configs写法也已经失效，把shared-configs:改写成spring.config.import方式即可
可以分享下你的配置吗？想参考参考下 谢谢你
--
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: notifications-unsubscribe@seata.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@seata.apache.org
For additional commands, e-mail: notifications-help@seata.apache.org