No channel is available for resource[jdbc:postgresql://[ip]:[port]/db?currentSchema=public] as alternative of Service1:[ip]:[port]

[song-we]

• [✓] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

大佬们帮忙看下，谢谢！！！
seata版本1.7.x，使用AT模式，store.mode=db
开启全局事务A，全局事务内有2个分支事务，分支事务1调用methodA1，分支事务2调用 methodA2。
methodA1调用成功，methodA2 发生异常，开始全局事务回滚；
此时报错：No channel is available for resource[jdbc:postgresql://[ip]:[port]/db?currentSchema=public] as alternative of Service1:[ip]:[port]

Ⅱ. Describe what happened

![微信图片_20250106171533](https://github.com/user-attachments/assets/6ee0235b-ecfb-4626-b71f-56c68cc654b3)

[funky-eyes]

rm日志和server日志完整发一下看看
Send the rm log and server log in their entirety.

[song-we]

rm日志和server日志完整发一下看看 Send the rm log and server log in their entirety.

全局事务ID：10.244.37.247:8091:4504185278260924839

seata-server采用集群部署的，部署了3个服务，这是3个服务的日志
seata-log-1 - 副本.txt
seata-log-2 - 副本.txt
seata-log-3 - 副本.txt

RM日志：目前我拿不到。我大概描述一下
TM中开启全局事务，事务内依次 调用serviceA，serviceB，serviceC，调用serviceC时报错，导致全局回滚。

[funky-eyes]

没有rm日志无法判断jdbcurl到底是什么

[funky-eyes]

还有一种可能rm连接到server是走的代理连接，不是直连，所以下发时找不到对应channel

[song-we]

没有rm日志无法判断jdbcurl到底是什么

感谢回复，我从elk拷贝了点日志，您先看一下。
rm-log.log

[funky-eyes]

rm如何连接的三台tc？rm的真实url是否与tc日志中的resource一致？
How does RM connect to the three TCs? Is the real URL of RM the same as the resource in the TC logs?

[funky-eyes]

你为什么把tc的日志拷下来说是rm的日志？
Why did you copy the log of tc and say it was the log of rm?