[email protected] wrote:
Related to previous post: Infinite loop in ChunkedInputStream.close
Oleg,
Last week I posted about an issue where we got the request body, and
when close is called on the input stream it gets to the underlying
InputStream.read and just sits there.
We ran some more tests with httpclient wire logging on and we captured a
slightly different issue but stemming from the same apparent underlying
call.
Both the previous issue and this one are both sitting idle at a call to
SocketInputStream.read (see the 'Client Log' further down this post
showing the stack trace where it is sitting).
From what I see below it looks like the reply started to come, we get
the headers.. but it is sitting idle while checking for the response
body.
The VM isn't paused tho because the IdleConnectionHandler is continuing
to fire and (I think) eventually is responsible for closing the
connection. That is why we aren't getting a connection reset from the
loadbalancer in this case.
So what in the world would would cause it to sit there?
The method blocks because the server is not sending any data whereas it
clearly should be sending at least the closing chunk.
I do not see anything that could suggest there is a problem on the
client side.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
