Hi All
Got this issue resolved by setting the expiry time to be smaller than
the socket time out, which was set explicitly before returning to the
pool. Now all looks good!
regards
asankha
On 03/21/2013 07:41 PM, Asankha C. Perera wrote:
Hi All
Should we internally update the socket timeout on the pooled
connection when one calls PoolEntry.updateExpiry()?
Also, I am trying to fix a corner case bug, where we submit a request
through the HttpAsyncRequester.execute(). There is a connection in the
pool, which is later found to have timed out - shouldn't the system
automatically get a new connection and attempt the send?
regards
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
