I found that we are not calling releaseConnection and I think it's somehow related to that. But it still doesn't explain the below behaviour where B responded 10 secs before A timedout. Is this some kind of a race condition when releaseConnection is not called?
On Fri, Jan 27, 2012 at 4:07 PM, Mohit Anchlia <[email protected]> wrote: > We are seeing a wierd behaviour and I am wondering if some kind of > session stickyness might be in play. > > We use HttpClient in Jboss to send post request from A -> B, then B -> > replies with 404 but after 15 secs (timeout on the request) we get > below timeout even though B -> replied to A in few millisecs. I can > see in B (apache) logs that response was sent in few ms. So don't > understand what is causing the timeout and why. > > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at > com.sun.net.ssl.internal.ssl.InputRecord.readFully(InputRecord.java:293) > at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:331) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
