Description of changes:
This exception can be thrown if the DNS for the configuration endpoint doesn't resolve. It possible that the DNS may take some time to updated and in those situations the UnresolvedAddressException will be thrown on the ch.connect(sa) call line 479.
Currently if this exception is thrown the SocketChannel gets leaked because the sockets and never cleaned up after the exception is thrown.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: N/A
Description of changes: This exception can be thrown if the DNS for the configuration endpoint doesn't resolve. It possible that the DNS may take some time to updated and in those situations the UnresolvedAddressException will be thrown on the
ch.connect(sa)call line 479.Currently if this exception is thrown the SocketChannel gets leaked because the sockets and never cleaned up after the exception is thrown.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.