On Wed, 2008-07-16 at 10:32 +0530, Jawahar Nayak wrote:
Hi,
I am using HttpClient3.0. To set retry handler I am using
clientParams.setParameter(HttpMethodParams.RETRY_HANDLER, 3);
This is wrong. See
http://hc.apache.org/httpclient-3.x/exception-handling.html#Custom_exception_handler
Hi Oleg!
Thanks for your response.
What can i do to force the socket to be closed? I don't want it to
remain open for a uncertain time - this could lead to a problem...
greetings,
Michael
Oleg Kalnichevski schrieb:
On Tue, 2008-07-15 at 11:09 +0200, Michael Mangeng wrote:
Hi all!
On
On Wed, 2008-07-16 at 16:24 +0200, Michael Mangeng wrote:
Hi Oleg!
Thanks for your response.
What can i do to force the socket to be closed? I don't want it to
remain open for a uncertain time - this could lead to a problem...
You can
(1) abort the request causing it to force close
Hi,
Our application is using HttpClient 3.0.1 and is experiencing long wait
times (started happening recently it seems) in the method
MultiThreadedHttpConnectionManager.doGetConnection(...). To give a summary
of the application, we have a bunch of threads (message driven beans, JBoss
4.0.2, JDK
Hi,
Our application is using HttpClient 3.0.1 and is experiencing long wait
times (started happening recently it seems) in the method
MultiThreadedHttpConnectionManager.doGetConnection(...). To give a summary
of the application, we have a bunch of threads (message driven beans, JBoss
4.0.2, JDK
Hi All,
I am having trouble in using HTTPClient 3.1 for PUT method w/
Expect:100-Continue header.
My requirement is that,
[1] client sends a PUT request to the server with header only using this Expect
header and waits for the 100 response back from the server.
[2] Then client sends the
