BufferedInputStream#fill() hanging in SocketInputStream#read0()
Alan.Bateman at oracle.com
Tue Sep 7 15:42:10 UTC 2010
Chris Hegarty wrote:
> This stacktrace is exactly the same as what you will see if the server
> does not respond. The HTTP client is trying to read the initial
> response, but there is none. Is possible that the server is eagerly
> accepting the connection but not processing it?
I think you're right, in which case changing BIS isn't going to help. If
the server doesn't close the connection, and it's not terminated
abruptly, then I assume the only way to recover in a reasonable time is
to have set the read timeout.
More information about the core-libs-dev