Re: Transfer failed in an IPv6-only (+NAT64) environment
Hi, .On 05/06/2024 11:48, Tamás Cservenák wrote: Howdy, Thanks for sharing! PS: We are not authoring the JDK bug, but good to have this in list. Can someone with write permission update that page https://cwiki.apache.org/confluence/display/MAVEN/ConnectException with more up to date alternatives? On Wed, Jun 5, 2024 at 8:49 AM Willy Manga wrote: . On 31/05/2024 17:46, Willy Manga wrote: Hi, On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X java.net.preferIPv6Addresses=system is even better. You let the OS handle that part. [...] -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
Howdy, Thanks for sharing! PS: We are not authoring the JDK bug, but good to have this in list. T On Wed, Jun 5, 2024 at 8:49 AM Willy Manga wrote: > . > On 31/05/2024 17:46, Willy Manga wrote: > > Hi, > > > > On 31/05/2024 17:11, Tamás Cservenák wrote: > >> And one more hint: > >> > >> See https://bugs.openjdk.org/browse/JDK-8311547 > >> and read about java.net.preferIPv6Addresses Java system property... > >> > >> Also, try to invoke Maven as: > >> MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X > > java.net.preferIPv6Addresses=system > > is even better. You let the OS handle that part. > > > > -- > Willy Manga > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Transfer failed in an IPv6-only (+NAT64) environment
. On 31/05/2024 17:46, Willy Manga wrote: Hi, On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X java.net.preferIPv6Addresses=system is even better. You let the OS handle that part. -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 Regarding this issue, I don't know where is the best place to raise it but there are 3 contexts: - IPv4-only - dual-stack - and ... IPv6-only because this comment [1]seems to not consider the last case. 1. https://bugs.openjdk.org/browse/JDK-8311547?focusedId=14594731&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14594731 -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
Hi, On 31/05/2024 17:11, Tamás Cservenák wrote: And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X Thanks for the pointer. It solved the issue on transfer. I have a compilation failure now but I guess it's now related to missing packages on my side. Regarding my version of Maven, I tend to stick to whatever the operating system have in the main repository. I will upgrade at least to debian 12 ; it comes with maven 3.8.7 [1] . But once again, thank you. 1. https://packages.debian.org/bookworm/maven -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Transfer failed in an IPv6-only (+NAT64) environment
And read this as well, Java is nicely covered: https://www.reddit.com/r/ipv6/comments/scvuy0/what_devices_do_you_know_of_that_dont_support/ T On Fri, May 31, 2024 at 3:11 PM Tamás Cservenák wrote: > And one more hint: > > See https://bugs.openjdk.org/browse/JDK-8311547 > and read about java.net.preferIPv6Addresses Java system property... > > Also, try to invoke Maven as: > MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X > > (to pass to JVM to prefer IPv6 addresses) > > Thanks > T > > On Fri, May 31, 2024 at 3:02 PM Tamás Cservenák > wrote: > >> Howdy, >> >> Unsure why, but: >> - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT >> (especially transfer) related bugs were fixed down the road since 3.6.3. >> - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand >> relies on (probably old) Apache HttpClient >> - still, it seems Java TCP stack have issues to use your network as >> stated in cause "java.net.SocketException: Network is unreachable (connect >> failed)" >> - you should verify is Java capable at all to use your network, as if it >> cannot, Maven hardly can help here. >> >> Google for Java and IPv6 as there are a lot of SO and other hits that >> showcases how to figure out (using Java simple code snippets) what may be >> the problem. >> >> Thanks >> T >> >> On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: >> >>> Hi, >>> >>> >>> I want to build guacamole-client as explained in the mainstream >>> repository[0] but the transfer failed as you can see here[1]. >>> >>> My environment: >>> - maven 3.6.3-5 (running on debian 11) >>> - IPv6-only with a NAT64 gateway in the network. >>> >>> >>> Someone in the guacamole user mailing-list suggested it might be an >>> issue with how either my network is setup or "some java incompatibilty" >>> [2] . >>> >>> I don't see on my side what can be wrong with the network. I was able to >>> retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I >>> don't know if during the execution of 'mvn package' something is pulling >>> resource from a hard-coded address. If that's the case it can explained >>> the failure. >>> >>> Any guidance appreciated. >>> >>> Thanks. >>> >>> >>> 0. https://github.com/apache/guacamole-client >>> >>> 1. http://paste.debian.net/1318665/ >>> >>> 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms >>> >>> >>> -- >>> Willy Manga >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>>
Re: Transfer failed in an IPv6-only (+NAT64) environment
And one more hint: See https://bugs.openjdk.org/browse/JDK-8311547 and read about java.net.preferIPv6Addresses Java system property... Also, try to invoke Maven as: MAVEN_OPTS="-Djava.net.preferIPv6Addresses=true" mvn package -X (to pass to JVM to prefer IPv6 addresses) Thanks T On Fri, May 31, 2024 at 3:02 PM Tamás Cservenák wrote: > Howdy, > > Unsure why, but: > - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT > (especially transfer) related bugs were fixed down the road since 3.6.3. > - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand > relies on (probably old) Apache HttpClient > - still, it seems Java TCP stack have issues to use your network as stated > in cause "java.net.SocketException: Network is unreachable (connect failed)" > - you should verify is Java capable at all to use your network, as if it > cannot, Maven hardly can help here. > > Google for Java and IPv6 as there are a lot of SO and other hits that > showcases how to figure out (using Java simple code snippets) what may be > the problem. > > Thanks > T > > On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: > >> Hi, >> >> >> I want to build guacamole-client as explained in the mainstream >> repository[0] but the transfer failed as you can see here[1]. >> >> My environment: >> - maven 3.6.3-5 (running on debian 11) >> - IPv6-only with a NAT64 gateway in the network. >> >> >> Someone in the guacamole user mailing-list suggested it might be an >> issue with how either my network is setup or "some java incompatibilty" >> [2] . >> >> I don't see on my side what can be wrong with the network. I was able to >> retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I >> don't know if during the execution of 'mvn package' something is pulling >> resource from a hard-coded address. If that's the case it can explained >> the failure. >> >> Any guidance appreciated. >> >> Thanks. >> >> >> 0. https://github.com/apache/guacamole-client >> >> 1. http://paste.debian.net/1318665/ >> >> 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms >> >> >> -- >> Willy Manga >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >>
Re: Transfer failed in an IPv6-only (+NAT64) environment
Howdy, Unsure why, but: - you use Maven 3.6.3 while the latest (bugfix) release is 3.9.7. A LOT (especially transfer) related bugs were fixed down the road since 3.6.3. - due 3.6.3 you use (probably old) Wagon transfer, that on the other hand relies on (probably old) Apache HttpClient - still, it seems Java TCP stack have issues to use your network as stated in cause "java.net.SocketException: Network is unreachable (connect failed)" - you should verify is Java capable at all to use your network, as if it cannot, Maven hardly can help here. Google for Java and IPv6 as there are a lot of SO and other hits that showcases how to figure out (using Java simple code snippets) what may be the problem. Thanks T On Fri, May 31, 2024 at 2:37 PM Willy Manga wrote: > Hi, > > > I want to build guacamole-client as explained in the mainstream > repository[0] but the transfer failed as you can see here[1]. > > My environment: > - maven 3.6.3-5 (running on debian 11) > - IPv6-only with a NAT64 gateway in the network. > > > Someone in the guacamole user mailing-list suggested it might be an > issue with how either my network is setup or "some java incompatibilty" > [2] . > > I don't see on my side what can be wrong with the network. I was able to > retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I > don't know if during the execution of 'mvn package' something is pulling > resource from a hard-coded address. If that's the case it can explained > the failure. > > Any guidance appreciated. > > Thanks. > > > 0. https://github.com/apache/guacamole-client > > 1. http://paste.debian.net/1318665/ > > 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms > > > -- > Willy Manga > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Transfer failed in an IPv6-only (+NAT64) environment
Hi, I want to build guacamole-client as explained in the mainstream repository[0] but the transfer failed as you can see here[1]. My environment: - maven 3.6.3-5 (running on debian 11) - IPv6-only with a NAT64 gateway in the network. Someone in the guacamole user mailing-list suggested it might be an issue with how either my network is setup or "some java incompatibilty" [2] . I don't see on my side what can be wrong with the network. I was able to retrieve manually build-helper-maven-plugin-3.2.0.pom using wget. But I don't know if during the execution of 'mvn package' something is pulling resource from a hard-coded address. If that's the case it can explained the failure. Any guidance appreciated. Thanks. 0. https://github.com/apache/guacamole-client 1. http://paste.debian.net/1318665/ 2. https://lists.apache.org/thread/xh31qjn3fwv7llz3dtc31n0d5pks5jms -- Willy Manga - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
