关于事务莫名回滚, LCN 4.1.0

- [x] 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
基于SpringCloud, Springboot 1.5.7, LCN 4.1.0
应用A 发起事务, 请求应用B, 应用B执行成功, 应用A拿到正确结果, 应用A执行完毕, 成功, 并发送消息, state值为1, TX-MANAGE收到该信息, 然后, TX-MANAGER 就出现了Transaction not over, all transactions must be rollback, 然后应用B, 就打印出了 rollback的消息, 事务回滚, 应用A也响应的回滚了.

应用A, B 都正确的处理了业务逻辑, 确定没有任何异常, 也没有try catch;

曾试图修改打开补偿事务, 并修改补偿事务时间为15000ms, 无效.
曾试图修改业务模块与TXManager之间的最大等待时间delaytime=15sec, 依然无效.

值得一提的是: 在本地开发环境运行毫无问题, 部署到linux环境后, 必现, 现在毫无头绪,

望得到一些线索, 谢谢.

### 2. Environment:
- JDK version: 1.8.0_144
- OS: Linux version 3.10.0-957.5.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Feb 1 14:54:57 UTC 2019
- TX-LCN version: 4.1.0
- Others:

### 3. Exception Stacktrace
无任何异常
```
Paste your Exception Stacktrace here!
```

### 4. Tour Idea

Start with the reported TX-MANAGER message, the application A/B transaction flow, and the Linux deployment environment described in the issue. Compare the local and Linux configurations and collect TX-MANAGER and application logs around the state=1 message and rollback. Done means identifying why the transaction is considered unfinished and documenting or fixing the cause; the issue currently provides no stack trace or named test.

Vom Indexierungsmodell aus dem Issue-Text verfasst.