Date: Mon, 05 Aug 2024 16:33:40 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 239890] java/openjdk11: openjdk 11.0.4+11.2 JDBC connections fail with IPv6 addresses Message-ID: <bug-239890-8522-vQq79c2VP5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239890-8522@https.bugs.freebsd.org/bugzilla/> References: <bug-239890-8522@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239890 --- Comment #11 from antonfb@hesiod.org --- I've notice this failure started when I upgraded to 14.1 from 13.2. I've also noticed some issues, not clear they are the same when going from 13.2 to 13.3. I looked at the kernel tcp code and I believe it started enforcing that you can not used 4 in 6 addresses for connect when v6only is 1. I think 13.2 didn't enforce that for connect when it did for bind. Things with java seem to work with preferipv4stack=false AND sysctl ipv6only=0, but other utilities on the system have problems with that. My use of tomcat is a problem here. Needing ipv6 support and jdbc together seem to require this combination. I do think, and I may try to debug, that jdk should be setting a new socket's v6only option to v6only=0 when the ip stack being used is ipv6. I wonder if running jdk in a jail where that jail sets the sysctl v6only to 0 might solve the issue for me. But having to look at this for every os upgrade is bad. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239890-8522-vQq79c2VP5>