hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris McClung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1634) Httpclient RequestConfig Timeout not occuring
Date Wed, 18 Mar 2015 15:37:38 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367328#comment-14367328
] 

Chris McClung commented on HTTPCLIENT-1634:
-------------------------------------------

Apologies, the description was too focused on what I was trying to do rather than the problem.

I added extra logging using the 4.3.6 release code and can now see that the requests hit the
following lines in InternalHttpClient:

Line 168: config is still null
Line 174: We get the params from request.getParams - this is not empty

So because RequestConfig is getting constructed at line 174 and set at line 181 it is not
using the supplied RequestConfig (line 147 is never called). 

I'll have a further look tomorrow and report back what I find.

> Httpclient RequestConfig Timeout not occuring
> ---------------------------------------------
>
>                 Key: HTTPCLIENT-1634
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1634
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: 4.3.6, 4.4 Final
>         Environment: Java 8, tomcat 8, Resteasy 3.0.X
>            Reporter: Chris McClung
>            Priority: Minor
>
> I have a project that uses HttpClient with Resteasy 3.  On shutdown an app makes a rest
call to unregister itself from another app that lives on the same Tomcat instance.
> I create the HttpClient instance being called by using the RequestConfig Builder and
use that to populate the HttpClient.
> The problem is that although HttpClient manages to establish a connection, it is immediately
closed on the server end and it does not time out.
> But if I modify the Resteasy code to set the requestConfig of the HttpPost etc instance
of HttpRequestBase with the same RequestConfig instance as the httpClient got, I get a timeout.
> It seems odd that I need to pass in the requestConfig to the httpPost object, so I'm
checking this isn't a bug.
> A note about Resteasys usage of the client:
> Resteasy 3 uses the httpClient if it is supplied one, using the HttpClient interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message