@huadong Thank you for your answer.
But I'm not using dubbo v2.6.x right now, because I was using v2.6.2 and the
graceful shutdown of dubbo was still a problem in tomcat, which is probably why
you said it.
I'm now rolling back to v2.5.10 to solve this problem using the following
solution
The code is as follows:
` ProtocolConfig.destroyAll();
`
` Field field = NettyClient.class.getDeclaredField("channelFactory");
`
` field.setAccessible(true);
`
` ChannelFactory channelFactory = (ChannelFactory)
field.get(NettyClient.class);
`
` channelFactory.releaseExternalResources();
`
` field.setAccessible(false);
`
[ Full content available at:
https://github.com/apache/incubator-dubbo/issues/2326 ]
This message was relayed via gitbox.apache.org for [email protected]
