RE: Response timeout issue

2019-06-27 Thread Joan grupoventus
Great Oleg! Issue raised: https://issues.apache.org/jira/browse/HTTPCLIENT-1998 Thanks, Joan. -Original Message- From: Oleg Kalnichevski Sent: Thursday, June 27, 2019 11:58 AM To: httpclient-users@hc.apache.org Subject: Re: Response timeout issue On Wed, 2019-06-26 at 15:52 +0200

Re: Response timeout issue

2019-06-27 Thread Oleg Kalnichevski
On Wed, 2019-06-26 at 15:52 +0200, Joan grupoventus wrote: > Hi Oleg, > > Regarding this pending issue about response timeout, I could finally > get traces. > > Our response timeout is set to 2,000ms. This is a request that ended > up with a response timeout: >

RE: Response timeout issue

2019-06-26 Thread Joan grupoventus
Hi Oleg, Regarding this pending issue about response timeout, I could finally get traces. Our response timeout is set to 2,000ms. This is a request that ended up with a response timeout: 62.xxx.xxx.xxx,23:59:47.606,A,1,A,5,A,4,B,,10.15.15.18:8081,,273,569,0,776,http.responseTimeout,23:59:48.382

Re: Response timeout issue

2019-06-07 Thread Oleg Kalnichevski
--- Oleg > Joan. > > > > Thanks, > > > > Joan. > > > > -Original Message- > > From: Oleg Kalnichevski > >

RE: Response timeout issue

2019-06-07 Thread Joan grupoventus
u but avoiding trace the request and response messages? Joan. > Thanks, > > Joan. > > -Original Message- > From: Oleg Kalnichevski > Sent: Friday, June 7, 2019 4:00 PM > To: HttpClient User Discussion > Subject: Re: Response timeout issue > > On Thu

Re: Response timeout issue

2019-06-07 Thread Oleg Kalnichevski
lse (like updating the capacity) I have to take > into account in the ' AsyncResponseConsumer ' to avoid hanging the > execution? > I need to see a log of such 'hanging' message exchnage. Oleg > Thanks, > > Joan. > > -Original Message----- > From: Oleg Kal

RE: Response timeout issue

2019-06-07 Thread Joan grupoventus
mer ' to avoid hanging the execution? Thanks, Joan. -Original Message- From: Oleg Kalnichevski Sent: Friday, June 7, 2019 4:00 PM To: HttpClient User Discussion Subject: Re: Response timeout issue On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote: > Hi again, > > No

Re: Response timeout issue

2019-06-07 Thread Oleg Kalnichevski
On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote: > Hi again, > > Not sure if we have seen something strange in the current test with > the keep alive connections. It's just a GET method to get a gif (this > pool has no keep-alive, that means a 100ms keep-alive). Here the > complete http

Re: Response timeout issue

2019-06-06 Thread Oleg Kalnichevski
On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote: > Hi again, > > Not sure if we have seen something strange in the current test with > the keep alive connections. It's just a GET method to get a gif (this > pool has no keep-alive, that means a 100ms keep-alive). Here the > complete http

RE: Response timeout issue

2019-06-06 Thread Joan grupoventus
Hi again, Not sure if we have seen something strange in the current test with the keep alive connections. It's just a GET method to get a gif (this pool has no keep-alive, that means a 100ms keep-alive). Here the complete http log: https://github.com/joanbalaguero/HttpClient.git (it's the

RE: Response timeout issue

2019-06-06 Thread Joan grupoventus
it be 1500 at least? Thanks, Joan. -Original Message- From: Oleg Kalnichevski Sent: Thursday, June 6, 2019 3:15 PM To: HttpClient User Discussion Subject: Re: Response timeout issue On Thu, 2019-06-06 at 14:34 +0200, Joan grupoventus wrote: > No .. that's the point ... we are tr

Re: Response timeout issue

2019-06-06 Thread Oleg Kalnichevski
> > -Original Message- > From: Oleg Kalnichevski > Sent: Thursday, June 6, 2019 2:27 PM > To: HttpClient User Discussion > Subject: Re: Response timeout issue > > On Wed, 2019-06-05 at 16:19 +0200, Joan grupoventus wrote: > > Hi Oleg, > > > > S

RE: Response timeout issue

2019-06-06 Thread Joan grupoventus
will know in what side the issue is. We'll try to do this today ... I'll keep you informed. Thanks, Joan. -Original Message- From: Oleg Kalnichevski Sent: Thursday, June 6, 2019 2:27 PM To: HttpClient User Discussion Subject: Re: Response timeout issue On Wed, 2019-06-05 at 16:19

Re: Response timeout issue

2019-06-06 Thread Oleg Kalnichevski
On Wed, 2019-06-05 at 16:19 +0200, Joan grupoventus wrote: > Hi Oleg, > > Still dealing with this stuck connections. I could get traces from > httpClient5 and we see all connections busy: > 08:12:56.031 ex-00E1DFB8: acquiring connection with route {}-> > http://10.15.15.14:8082 > 08:12:56.087

RE: Response timeout issue

2019-06-05 Thread Joan grupoventus
t with the alive instances from "org.apache.hc" when the pool was exhausted. Any help would be really appreciated. Thanks, Joan. -Original Message- From: Oleg Kalnichevski Sent: Thursday, May 30, 2019 11:40 AM To: HttpClient User Discussion Subject: Re: Response timeout is

Re: Response timeout issue

2019-05-30 Thread Oleg Kalnichevski
started Tomcat, we could only get a thread stack ... not > sure if this can be of any utility but I could attach it ... > > Thanks, > > Joan. > > > -Original Message- > From: Oleg Kalnichevski > Sent: Monday, May 27, 2019 11:10 PM > To: HttpClient User Dis

RE: Response timeout issue

2019-05-29 Thread Joan grupoventus
, 2019 11:10 PM To: HttpClient User Discussion Subject: Re: Response timeout issue Joan Please raise a JIRA for this issue and attach a wire log with time stamps of a _complete_ message exchange demonstrating the incorrect behavior. I will review connection management code tomorrow. Oleg

Re: Response timeout issue

2019-05-27 Thread Oleg Kalnichevski
Joan Please raise a JIRA for this issue and attach a wire log with time stamps of a _complete_ message exchange demonstrating the incorrect behavior. I will review connection management code tomorrow. Oleg On Mon, 2019-05-27 at 19:33 +0200, Joan ventusproxy wrote: > Hello, > > � > > We

Response timeout issue

2019-05-27 Thread Joan ventusproxy
Hello, � We are having an issue with HttpClient 5 beta4 / HttpCore 5 Beta7 and socket timeout after switching from asyncClient 1.3. � Our requests have a response timeout of 4 seconds. When a response timeout occurs we see this in our log: 2019-05-27 13:05:35 � � � � [62.73.191.161]