Skip to content
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

netty resolver may get ipv6 addresses even when only ipv4 is available #1570

Closed
alexlehm opened this issue Aug 9, 2016 · 4 comments
Closed

netty resolver may get ipv6 addresses even when only ipv4 is available #1570

alexlehm opened this issue Aug 9, 2016 · 4 comments

Comments

@alexlehm
Copy link
Contributor

@alexlehm alexlehm commented Aug 9, 2016

Following up on this groups thread https://groups.google.com/d/topic/vertx/7xTo_a_lOWk/discussion, it is necessary to switch to the next netty version 4.1.5 when it becomes available to get fix for the issue that the resolver might get a ipv6 address even though only ipv4 is available and is unable to connect to the address. This behaviour is switched off by -Djava.net.preferIPv4Stack=true, which was not honoured by the new resolver in netty 4.1.

The netty issue for the issue is netty/netty#5657

@pmlopes pmlopes mentioned this issue Aug 9, 2016
58 of 60 tasks complete
@alexlehm

This comment has been minimized.

Copy link
Contributor Author

@alexlehm alexlehm commented Aug 10, 2016

issue is resolved in netty 4.1 branch

@vietj

This comment has been minimized.

Copy link
Contributor

@vietj vietj commented Sep 7, 2016

we can close this issue, right ?

@alexlehm

This comment has been minimized.

Copy link
Contributor Author

@alexlehm alexlehm commented Sep 7, 2016

yes, sorry i forgot about this issue. this was fixed with the netty update to 4.1.5

@alexlehm

This comment has been minimized.

Copy link
Contributor Author

@alexlehm alexlehm commented Sep 7, 2016

resolved by netty 4.1.5

@alexlehm alexlehm closed this Sep 7, 2016
xiahome added a commit to xiahome/ambry that referenced this issue Apr 5, 2017
with ipv6 (its dnsnameresolver could not parse if the underlying jvm
only prefers ipv4). The issue got fixed in 4.1.5.

Link to more details of the issue
eclipse-vertx/vert.x#1570

built and tested
xiahome added a commit to xiahome/ambry that referenced this issue Apr 5, 2017
This is to bring in Netty's fix to the ipv6 issue. Netty has some issue
with ipv6 (its dnsnameresolver could not parse if the underlying jvm
only prefers ipv4). The issue got fixed in 4.1.5.

Link to more details of the issue
eclipse-vertx/vert.x#1570

built and tested
vgkholla added a commit to linkedin/ambry that referenced this issue Apr 5, 2017
This is to bring in Netty's fix to the ipv6 issue. Netty has some issue
with ipv6 (its dnsnameresolver could not parse if the underlying jvm
only prefers ipv4). The issue got fixed in 4.1.5.

Link to more details of the issue
eclipse-vertx/vert.x#1570
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.