Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpClient User Discussion" <httpclient-users@hc.apache.org>
Subject: Re: Getting SocketTimeoutException after a very short amount of time
References: <55E3BE59.8070305@elyograg.org>
 <1441011726.27084.4.camel@apache.org> <55E87BDC.5010402@elyograg.org>
 <55E89BE9.6060108@elyograg.org> <1441374791.12559.2.camel@apache.org>
 <55E9D764.8060106@elyograg.org>
To: HttpClient User Discussion <httpclient-users@hc.apache.org>
From: Shawn Heisey <apache@elyograg.org>
Message-ID: <55E9DA4B.5060406@elyograg.org>
Date: Fri, 4 Sep 2015 11:52:11 -0600
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E9D764.8060106@elyograg.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 9/4/2015 11:39 AM, Shawn Heisey wrote:
> I must be creating the client objects incorrectly for the "set socket
> timeout" message to never be logged.

I checked the ClientConfiguration.java example, and found that it sets
the socket timeout when it is building the HttpGet object, not the
HttpClient object.

In my program, I have absolutely no control over the GET/POST requests,
that is deep in the bowels of SolrJ.

As a committer on Lucene/Solr, I *do* have the ability to change SolrJ,
and perhaps these parameters should be configured in our SolrClient
object and actually set when the request objects are created, but I
think it should be possible to set them on the HttpClient object and
have all requests utilize those defaults.

Thanks,
Shawn


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