We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
阿里云服务器启动了3个网关服
其中 服务器启动的端口 和 种子信息 都以json配置进行获取
其中xx.xx.xx.xx 为真实的外网ip
分别运行 java -jar spring-game-broker-1.0.0.jar 1 java -jar spring-game-broker-1.0.0.jar 2 java -jar spring-game-broker-1.0.0.jar 3
启动3个网关服务器
对外服代码如下:
正常连接3个网关
2024-11-11T00:22:42.941+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20003
2024-11-11T00:22:43.955+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20002
2024-11-11T00:22:44.973+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20001
The text was updated successfully, but these errors were encountered:
debug 跟下,或到 bolt 社区问下。
Sorry, something went wrong.
No branches or pull requests
你的问题 | 使用场景
阿里云服务器启动了3个网关服
其中 服务器启动的端口 和 种子信息 都以json配置进行获取
其中xx.xx.xx.xx 为真实的外网ip
分别运行
java -jar spring-game-broker-1.0.0.jar 1
java -jar spring-game-broker-1.0.0.jar 2
java -jar spring-game-broker-1.0.0.jar 3
启动3个网关服务器
对外服代码如下:
预期值
正常连接3个网关
实际值
2024-11-11T00:22:42.941+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20003
2024-11-11T00:22:43.955+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20002
2024-11-11T00:22:44.973+08:00 ERROR 536 --- [ Simple-28-3] c.i.g.b.b.core.client.BrokerClientItem : Create connection failed. The address is 172.30.129.58:20001
版本
The text was updated successfully, but these errors were encountered: