rm client is not connected一直在seata-server端报错

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

### Ⅰ. Issue Description

### Ⅱ. Describe what happened

应用运行一段时间后seata-server的global_table和branch_table会出现部分数据一直存在，导致seata-sever的日志一直打印，直到磁盘写满，但是数据是正常

```
Just paste your stack trace here!
```


### Ⅲ. Describe what you expected to happen

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. xxx
2. xxx
3. xxx

### Ⅴ. Anything else we need to know?

### Ⅵ. Environment:

- JDK version : 1.8
- OS : centos
- Others:

Start by reviewing the seata-server logs and the persistent rows in global_table and branch_table after the application has run for some time. The issue lacks reproduction steps, a stack trace, and named files or tests; completion would require identifying why these rows remain and verifying that repeated errors stop without filling the disk.

Written by the indexing model from the issue text.