codingapi / codingapi/tx-lcn

通讯超时锁表了

Open
#313 1 comment 0 reactions 0 assignees View on GitHub
v/preBug
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
A向库插数据,然后A->B,A->C:
当并发开到1000时候,当A->B,或者A->C出现调用超时的时候,A库锁表了,当A模块重启后恢复正常
并发数200,400,500都正常,设置到1000的时候出问题了

### 2. Environment:
- JDK version: 1.8
- OS: win10
- TX-LCN version: 5.0.2.release
- Others:

### 3. Exception Stacktrace
1. 常见的springboot ribbon调用超时报错,A模块提示连接B,C超时
2. DTXServiceExecutor: business code error @group(d93327fe8536)
注:内网不方便截取报错信息
Flipping property: spring
```
Paste your Exception Stacktrace here!
```

### 4. Tour Idea

Contributor guide

No contributing guide indexed for this repository

Research direction

The report names A/B/C modules, JDK 1.8, TX-LCN 5.0.2.release, Spring Boot Ribbon timeouts, and DTXServiceExecutor; no source file or test is provided. Start by reproducing the A→B/A→C timeout at concurrency 1000 and capture the missing exception details, then verify whether the lock clears without restarting module A.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.