You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
I have checked the FAQ of this repository and believe that this is not a duplicate.
Environment
Dubbo version: 2.7.0
Operating System version: mac
Java version: 1.8
Steps to reproduce this issue
AbstractClient#initConnectStatusCheckCommand set break point at !isConnected().
AbstractClient#close() set break point here.
start client first, start provider and then shutdown provider gracefully , let method AbstractClient.close() be executed. Then select step 1 and trigger the thread to execute !isConnected, here will always try to connect the offline machine.
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps?
When the server goes offline, the client will not reconnect the offline machine.
Actual Result
What actually happens?
The client reconnects the offline machine every 2 seconds and causes a large number of arp packets(because ip is recycled and not available now).
The text was updated successfully, but these errors were encountered:
Environment
Steps to reproduce this issue
AbstractClient#initConnectStatusCheckCommand
set break point at!isConnected()
.AbstractClient#close()
set break point here.AbstractClient.close()
be executed. Then select step1
and trigger the thread to execute!isConnected
, here will always try to connect the offline machine.Pls. provide [GitHub address] to reproduce this issue.
Expected Result
What do you expected from the above steps?
When the server goes offline, the client will not reconnect the offline machine.
Actual Result
What actually happens?
The client reconnects the offline machine every 2 seconds and causes a large number of arp packets(because ip is recycled and not available now).
The text was updated successfully, but these errors were encountered: