[
https://issues.apache.org/jira/browse/HTTPCLIENT-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367366#comment-14367366
]
Oleg Kalnichevski commented on HTTPCLIENT-1634:
-----------------------------------------------
One cannot mix deprecated, old style and new style config APIs. If one does,
old style config parameters take precedence.
Oleg
> 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: [email protected]
For additional commands, e-mail: [email protected]
