WangzJi commented on issue #7440:
URL:
https://github.com/apache/incubator-seata/issues/7440#issuecomment-2987563934
@YongGoose Hi
Based on my investigation of the build logs, the coverage drop in core
module after PR #7435 appears to be caused by port conflicts.
From the CI build logs, I found connection failures in core module tests:
```
2025-06-13T09:23:25.4242455Z 09:23:25.402 [main] INFO
org.apache.seata.core.rpc.netty.NettyClientChannelManager -- will connect to
127.0.0.1:8091
2025-06-13T09:23:25.4247915Z 09:23:25.403 [main] INFO
org.apache.seata.core.rpc.netty.RmNettyRemotingClient -- RM will register
:jdbc:xx://localhost/test
2025-06-13T09:23:25.4250828Z 09:23:25.404 [main] INFO
org.apache.seata.core.rpc.netty.NettyPoolableFactory -- NettyPool create
channel to transactionRole:RMROLE,address:127.0.0.1:8091,msg:<
RegisterRMRequest{resourceIds='jdbc:xx://localhost/test',
version='2.5.0-SNAPSHOT', applicationId='fail_fast',
transactionServiceGroup='default_tx_group', extraData='null'} >
2025-06-13T09:23:25.4280752Z 09:23:25.410 [configOperate_2_1_2] DEBUG
org.apache.seata.config.FileConfiguration -- Could not found property
transport.protocol, try to use default value instead. exception:No
configuration setting found for key 'transport.protocol'
2025-06-13T09:23:25.4283719Z 09:23:25.413 [configOperate_2_1_2] DEBUG
org.apache.seata.config.FileConfiguration -- Could not found property
transport.serialization, try to use default value instead. exception:No
configuration setting found for key 'transport.serialization'
2025-06-13T09:23:25.4286192Z 09:23:25.415 [NettyClientSelector_RMROLE_4_1_8]
INFO org.apache.seata.core.rpc.netty.AbstractNettyRemotingClient --
ChannelHandlerContext(AbstractNettyRemotingClient$ClientHandler#0, [id:
0x63cf5273]) will closed
2025-06-13T09:23:25.4288158Z 09:23:25.415 [main] ERROR
org.apache.seata.core.rpc.netty.NettyClientChannelManager -- 0304 register RM
failed.
2025-06-13T09:23:25.4289460Z
org.apache.seata.common.exception.FrameworkException: can not connect to
services-server.
2025-06-13T09:23:25.4290693Z at
org.apache.seata.core.rpc.netty.NettyClientBootstrap.getNewChannel(NettyClientBootstrap.java:212)
```
PR #7435: Introduced dynamic port allocation in server module
Core Module: Still uses hardcoded port 8091 for client connections
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
