LCN服务端异常导致被调用方事务不提交

在使用LCN事务时（TC version:5.0.2.RELEASE），A调用B A成功插入数据，B端已经打印插入SQL语句，且显示影响行数>1 ，但最后找不到该数据，初步判断B端事务未提交导致的问题。AB端无任何异常信息；后面查看服务端日志，发现有异常信息
An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handl
e the exception.
java.io.IOException: 没有到主机的路由
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.8.0_191]
java.io.IOException: Connection reset by peer

请问该问题是什么原因引起的，如何避免？

Start with the TC server logs and the A-to-B transaction flow described in the report, using tx-lcn 5.0.2.RELEASE. Trace the server-side handling around the reported "No route to host" and "Connection reset by peer" errors, then reproduce the case and verify whether B's inserted data is committed. Done means the failure cause and a documented prevention or recovery path are established.

Vom Indexierungsmodell aus dem Issue-Text verfasst.