I got the following log information. Obviously, after the heartbeat timeout, a new tcp connection is initiated.
*2019-10-25 06:52:48.723 INFO 1 --- [eCheck-thread-1] o.a.d.r.e.s.header.***ReconnectTimerTask*** : [DUBBO] Initial connection to HeaderExchangeClient [channel=org.apache.dubbo.remoting.transport.netty4.NettyClient [172.16.0.15:0 -> dubboprovider/10.247.251.34:20880]], dubbo version: 2.7.4, current host: 172.16.0.15 2019-10-25 06:52:48.731 INFO 1 --- [eCheck-thread-1] o.a.d.r.transport.netty4.NettyClient : [DUBBO] Close old netty channel [id: 0xe4e6a862, L:/172.16.0.15:36250 ! R:dubboprovider/10.247.251.34:20880] on create new netty channel [id: 0xa8c79251, L:/172.16.0.15:55844 - R:dubboprovider/10.247.251.34:20880], dubbo version: 2.7.4, current host: 172.16.0.15 2019-10-25 06:52:48.732 INFO 1 --- [eCheck-thread-1] o.a.d.remoting.transport.AbstractClient : [DUBBO] Succeed connect to server dubboprovider/10.247.251.34:20880 from NettyClient 172.16.0.15 using dubbo version 2.7.4, channel is NettyChannel [channel=[id: 0xa8c79251, L:/172.16.0.15:55844 - R:dubboprovider/10.247.251.34:20880]], dubbo version: 2.7.4, current host: 172.16.0.15* [ Full content available at: https://github.com/apache/dubbo/issues/5234 ] This message was relayed via gitbox.apache.org for [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
