Stack trace for reference: java.net.SocketInputStream.socketRead0 line: not available [native method] java.net.SocketInputStream.read line: 150 java.net.SocketInputStream.read line: 121 java.io.BufferedInputStream.fill line: 246 java.io.BufferedInputStream.read line: 265 com.sun.jndi.dns.DnsClient.continueTcpQuery line: 455 com.sun.jndi.dns.DnsClient.doTcpQuery line: 443 com.sun.jndi.dns.DnsClient.query line: 245 com.sun.jndi.dns.Resolver.query line: 81 com.sun.jndi.dns.DnsContext.c_getAttributes line: 434 com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getAttributes line: 235 com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes line: 141 com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getAttributes line: 129 javax.naming.directory.InitialDirContext.getAttributes line: 142
On Thu, 18 Jul 2019 at 11:32, Milan Mimica <milan.mim...@gmail.com> wrote: > > On Thu, 18 Jul 2019 at 11:23, Chris Hegarty <chris.hega...@oracle.com> wrote: > > > Have you ever considered the problem reported here: > > > https://stackoverflow.com/questions/14603553/dns-query-freezes-with-dnscontextfactory-in-java > > > > I posted a comment on that SO thread yesterday, no reply since. > > Hi Chris > > This exception must have been thrown from > DatagramSocket::receive(DatagramPacket p), not from TCP socket. So it > does not cover the case when TCP socket gets stuck, in the fallback > flow for truncated UDP responses. > > > -- > Milan Mimica -- Milan Mimica
