Yes, as Alan said the way IPv6 is set up in the JDK means that either
you have:
AF_INET sockets (which are IPv4 only) or
AF_INET6 sockets (which can be IPv4 or IPv6)
It's not possible to mix the two types. If inetd passes an AF_INET
socket on startup then the VM is stuck in IPv4 mode.
I've upd
On 29/11/2018 18:04, Bernd Eckenfels wrote:
Hello,
I wonder if that conclusion „stdin = tcp4 -> disable tcp6“ is correct
at all. The started program might serve a v4 connection but it still
could want to do ipv6 client connections.
If somebody wants to disable v4 they can do it regularly wi
Hello,
I wonder if that conclusion „stdin = tcp4 -> disable tcp6“ is correct at all.
The started program might serve a v4 connection but it still could want to do
ipv6 client connections.
If somebody wants to disable v4 they can do it regularly with the System
property.
Gruss
Bernd
--
http:/
On 29/11/2018, 17:19, Alan Bateman wrote:
On 28/11/2018 15:50, Michael McMahon wrote:
Could I get the following fix reviewed please?
The fix is pretty simple, but the test a bit more involved
since the issue occurs when the JVM is launched in unusual circumstances
where its stdin,out,err are con
On 28/11/2018 15:50, Michael McMahon wrote:
Could I get the following fix reviewed please?
The fix is pretty simple, but the test a bit more involved
since the issue occurs when the JVM is launched in unusual circumstances
where its stdin,out,err are connected to a UNIX domain socket.
This occurs
> On 28 Nov 2018, at 15:50, Michael McMahon
> wrote:
>
> Could I get the following fix reviewed please?
> The fix is pretty simple, but the test a bit more involved
> since the issue occurs when the JVM is launched in unusual circumstances
> where its stdin,out,err are connected to a UNIX domai
