apache / apache/incubator-seata
seata服务端版本是1.5.2,client端引用seata版本1.5.2,spring版本5.2.8.RELEASE,服务端启动正常,启动client端时报错,麻烦大佬帮忙看看
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
1.seata服务端版本是1.5.2,seata client版本1.5.2,spring版本5.2.8.RELEASE,spring boot版本2.3.2.RELEASE,服务端启动正常,启动client端时报错,错误如下:
***************************
APPLICATION FAILED TO START
***************************
Description:
Configuration property name 'seata.transport.rpcRmRequestTimeout' is not valid:
Invalid characters: 'R', 'R', 'T'
Reason: Canonical names should be kebab-case ('-' separated), lowercase alpha-numeric characters and must start with a letter
Action:
Modify 'seata.transport.rpcRmRequestTimeout' so that it conforms to the canonical names requirements.
2022-07-22 10:51:57.771 ERROR 19252 --- [ main] o.s.boot.SpringApplication : Application run failed
org.springframework.boot.context.properties.source.InvalidConfigurationPropertyNameException: Configuration property name 'seata.transport.rpcRmRequestTimeout' is not valid
at org.springframework.boot.context.properties.source.ConfigurationPropertyName.elementsOf(ConfigurationPropertyName.java:565) ~[spring-boot-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at org.springframework.boot.context.properties.source.ConfigurationPropertyName.elementsOf(ConfigurationPropertyName.java:542) ~[spring-boot-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at org.springframework.boot.context.properties.source.ConfigurationPropertyName.of(ConfigurationPropertyName.java:533) ~[spring-boot-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at org.springframework.boot.context.properties.source.ConfigurationPropertyName.of(ConfigurationPropertyName.java:510) ~[spring-boot-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at org.springframework.boot.context.properties.migrator.PropertiesMigrationReporter.lambda$null$1(PropertiesMigrationReporter.java:103) ~[spring-boot-properties-migrator-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at java.util.ArrayList.forEach(ArrayList.java:1259) ~[na:1.8.0_301]
at org.springframework.boot.context.properties.migrator.PropertiesMigrationReporter.lambda$getMatchingProperties$2(PropertiesMigrationReporter.java:101) ~[spring-boot-properties-migrator-2.3.2.RELEASE.jar:2.3.2.RELEASE]
at java.util.LinkedHashMap.forEach(LinkedHashMap.java:684) ~[na:1.8.0_301]
2.client端seata依赖如下:
io.seata
seata-spring-boot-starter
1.5.2
com.alibaba.cloud
spring-cloud-starter-alibaba-seata
2.2.1.RELEASE
io.seata
seata-spring-boot-starter
3.服务端配置放在nacos,如下:

4.client应用配置如下:
seata:
enabled: true
application-id: order-at-example
tx-service-group: my-tx-group # 事务群组(可以每个应用独立取名,也可以使用相同的名字)
registry:
type: nacos
nacos:
application: seata-server
group: SEATA_GROUP
server-addr: ${NACOS_SERVER_ADDR:127.0.0.1:8848}
namespace: ${NACOS_NAMESPACE:seata152}
#cluster: default
config:
type: nacos
nacos:
namespace: ${NACOS_NAMESPACE:seata152}
server-addr: ${NACOS_SERVER_ADDR:127.0.0.1:8848}
group: SEATA_GROUP
data-id: seataServer.properties
Contributor guide
Research direction
Start with Spring Boot's configuration-property validation and the client dependency declarations shown in the report. Check how seata-spring-boot-starter 1.5.2 and spring-cloud-starter-alibaba-seata 2.2.1.RELEASE process the reported property, then verify the client starts without the canonical-name failure using the listed application configuration.
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
- 35/100