Re: 4.0 does not retry when connect drop?

2008-01-17 Thread Jiang Qian
Hi Oleg thanks! I am debugging a NoHttpResponseException issue, and my initial thoughts was wrong, it is not related to retry. On Jan 17, 2008 4:10 PM, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > On Thu, 2008-01-17 at 15:16 -0800, Jiang Qian wrote: > > Hi, > > My last email was wrong

Re: 4.0 does not retry when connect drop?

2008-01-17 Thread Oleg Kalnichevski
On Thu, 2008-01-17 at 15:16 -0800, Jiang Qian wrote: > Hi, > My last email was wrong > it actually try to re open in above the > if (!managedConn.isOpen()) { > managedConn.open(route, context, params); > } > > Thanks > Jiang, What kind of

Re: 4.0 does not retry when connect drop?

2008-01-17 Thread Jiang Qian
Hi, My last email was wrong it actually try to re open in above the if (!managedConn.isOpen()) { managedConn.open(route, context, params); } Thanks On Jan 17, 2008 3:00 PM, Jiang Qian <[EMAIL PROTECTED]> wrote: > Hi, >Here is what I foun

4.0 does not retry when connect drop?

2008-01-17 Thread Jiang Qian
Hi, Here is what I found: in DefaultClientRequestDirector execute method line 348 if connection drop by server, it will throw NoHttpResponseException, then managedConn.close(); and this is allow to retry, so it rerun response = requestExec.execute(request, managedConn, context); goes to Ht