-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
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
lots of udp ports opening #881
Comments
@jchambers any solution on this issue? |
Hi @cyflhn I have the same issue, and finally I found that may be some netty packages were downgraded to lower versions caused by other dependencies. In my case, io.netty:netty-resolver-dns is downgraded to 4.1.29.Final, that caused too many udp ports opening, After I forced set the io.netty:netty-resolver-dns to a higher version, the issue resolved.
|
hi, @jianggaocheng |
@cyflhn Maybe other netty dependency is still low version? |
@jianggaocheng I am sure there is no other netty dependencies in our module. You can look into the source code of |
Folks, is this causing a practical problem? In the absence of actually harmful side effects, my thought is that the best way to address this is to get #540 done. |
@jchambers the number of opening udp ports is limited on a server, we need udp ports to resolve other domains. On the other hand, it is not necessary to open so many udp ports to resolve the same domain. it is a kind of big waste of udp resources. |
We have several apps which needs to send notifications to apns through pushy. We found that there are lots of udp ports opening on our servers. I checked the source code and found that all these ports are related to dns resolver in netty. For all
ApnsClient
objects, they share the sameNioEventLoopGroup
instance. But inAddressResolverGroup
of netty, it creates an instance ofInetSocketAddressResolver
for eachNioEventLoop
. I think it is the cause of so many opening udp ports. I don't think it is necessary to create so manyInetSocketAddressResolver
instances. Do you have ideas to optimize this issue?The text was updated successfully, but these errors were encountered: