You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Chris McClung (JIRA)" <ji...@apache.org> on 2015/03/17 15:03:38 UTC

[jira] [Created] (HTTPCLIENT-1634) Httpclient RequestConfig Timeout not occuring

Chris McClung created HTTPCLIENT-1634:
-----------------------------------------

             Summary: 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.4 Final, 4.3.6
         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