tx使用启动报错
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 1.4k
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] I have searched the [issues](https://github.com/codingapi/tx-lcn/issues) of this repository and believe that this is not a duplicate.
### 1. Bug Description
### 2. Environment:
- JDK version:
- OS:
- TX-LCN version:
- Others:
### 3. Exception Stacktrace
```
Paste your Exception Stacktrace here!
```
### 4. Tour Idea
Field existingConcurrencyStrategy in org.springframework.cloud.netflix.hystrix.security.HystrixSecurityAutoConfiguration required a single bean, but 2 were found:
- tracingHystrixConcurrencyStrategy: defined in URL [jar:file:/C:/Users/admin/.m2/repository/com/codingapi/txlcn/txlcn-tracing/5.0.2.RELEASE/txlcn-tracing-5.0.2.RELEASE.jar!/com/codingapi/txlcn/tracing/http/TracingHystrixConcurrencyStrategy.class]
- sleuthHystrixConcurrencyStrategy: defined by method 'sleuthHystrixConcurrencyStrategy' in class path resource [org/springframework/cloud/sleuth/instrument/hystrix/SleuthHystrixAutoConfiguration.class]
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the startup failure with TX-LCN 5.0.2.RELEASE and inspect the bean definitions in HystrixSecurityAutoConfiguration, TracingHystrixConcurrencyStrategy, and SleuthHystrixAutoConfiguration. Done means the application starts without the two-bean conflict while preserving the required Hystrix concurrency strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- 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