On Mon, 2013-02-04 at 22:25 +0100, Philippe Mouawad wrote:
> Hello,
>
> We had an issue reported in JMerer related to HttpClient version 4.X.X
> which does not happen in version 3.1.
>
> Thread dump shows thread hangs within InetAddress$1.getHostByAddr:
>
> "Thread Group 1-1" prio=6 tid=0x038f3c
UNSUBSCRIBE
Med vänliga hälsningar/Best regards
Benjamin Janes
--
Senior IT Specialist
Cata Technical Lead
Open Group Certified IT Specialist / Level 1 Certified IT Specialist
Technical Specialist (Master Data Management)
IBM Sverige AB
V. Varvsgatan 19, 211
Hi,
We are using HttpClient 4.2.3 to communicate to a third party Internet URL.
To debug any issue that comes during communication, we need to see the
debug logs generated by HttpClient classes (for example HttpAuthenticator
class).
I see that commons-logging-1.1.1.jar is shipped with HttpClient. B
On Mon, 2013-02-04 at 16:14 -0800, vigna wrote:
> I have create a non-keepalive client (no connection reuse) by
>
> httpClient.setReuseStrategy( new NoConnectionReuseStrategy() );
>
> Nonetheless, in the logs I get
>
> ClientConnectionManager - Connection can be kept alive for
> 9223372036854775
On Mon, 2013-02-04 at 23:43 -0800, Oliver Lorenz wrote:
> Hi,
>
> We are using httpcore 4.0.1 and httpclient 4.0.3 in one of our products. In
> a clients test environment, we experience a big delay when calling
> writeTo().
>
Is there a reason for using such an outdated version of HttpClient?
>
On Tue, 2013-02-05 at 15:39 +0530, Deepak Mishra wrote:
> Hi,
> We are using HttpClient 4.2.3 to communicate to a third party Internet URL.
> To debug any issue that comes during communication, we need to see the
> debug logs generated by HttpClient classes (for example HttpAuthenticator
> class).
Thanks for your reply Oleg.
You wrote:
> Is there a reason for using such an outdated version of HttpClient?
We have started to use it when it came out, and did not have a direct need
to upgrade. But we will plan for that.
> > As far as i understood the execute(), it blocks until the whole stre
On Tue, 2013-02-05 at 03:26 -0800, Oliver Lorenz wrote:
> Thanks for your reply Oleg.
>
> You wrote:
>
> > Is there a reason for using such an outdated version of HttpClient?
>
> We have started to use it when it came out, and did not have a direct need
> to upgrade. But we will plan for that.
>
Yes, this helped.
Thanks a lot!
Kind regards
Oliver
--
View this message in context:
http://httpcomponents.10934.n7.nabble.com/responseEntity-writeTo-performance-depending-on-network-tp19194p19211.html
Sent from the HttpClient-User mailing list archive at Nabble.com.
Is there a special log category that I can use to prove that we are waiting
for the network layer?
--
View this message in context:
http://httpcomponents.10934.n7.nabble.com/responseEntity-writeTo-performance-depending-on-network-tp19194p19212.html
Sent from the HttpClient-User mailing list arc
Hello everyone,
At the beginning, I had something like that :
HttpClient httpClient = new DefaultHttpClient();
HttpPost httpPost = new HttpPost(SOME_URL);
HttpResponse postResponse = httpClient.execute(httpPost);
It turns out that I got a 301 Moved permanently.
So I made the following modificati
On Tue, 2013-02-05 at 06:30 -0800, Oliver Lorenz wrote:
> Is there a special log category that I can use to prove that we are waiting
> for the network layer?
>
None I know of. Wireshark is your best friend.
Oleg
-
To unsubsc
Hey all, I've gotten further along and had some followup questions ...
I have a single httpclient instance now for the web application...
and I am now using the PoolingClientConnectionManager so I can easily do
Multiple-Threads at same time if needed, and now using the regular
HttpClient (ditched
On Tue, 2013-02-05 at 18:53 +0100, COURTAULT Francois wrote:
> Hello everyone,
>
> At the beginning, I had something like that :
> HttpClient httpClient = new DefaultHttpClient();
> HttpPost httpPost = new HttpPost(SOME_URL);
> HttpResponse postResponse = httpClient.execute(httpPost);
>
> It turn
On Tue, 2013-02-05 at 15:44 -0500, Arian wrote:
> Hey all, I've gotten further along and had some followup questions ...
>
> I have a single httpclient instance now for the web application...
> and I am now using the PoolingClientConnectionManager so I can easily do
> Multiple-Threads at same time
On Tue, 2013-02-05 at 23:41 +0100, Oleg Kalnichevski wrote:
> On Tue, 2013-02-05 at 15:44 -0500, Arian wrote:
> > Hey all, I've gotten further along and had some followup questions ...
> >
> > I have a single httpclient instance now for the web application...
> > and I am now using the PoolingClie
Hello everyone,
At the beginning, I had something like that :
HttpClient httpClient = new DefaultHttpClient();
HttpPost httpPost = new HttpPost(SOME_URL);
HttpResponse postResponse = httpClient.execute(httpPost);
It turns out that I got a 301 Moved permanently.
So I made the following modificati
Hi,
We are using HttpClient 4.2.3 to communicate to an internet URL through a
proxy server. Proxy server has NTLM authentication integrated with an
Active Directory.
We are able to do NTLM authentication with Ubuntu 12.04 Squid proxy server
but not able to do NTLM authentication with McAfee webgate
18 matches
Mail list logo
