Hi Oleg,
Thanks for your inputs. Now I am making a new HttpState object for each
request made. But have found a new problem. This problem occurs when the
requests are concurrent. What is evident is that after redirection happens the
JSESSIONID of both the requests become same. Could not
gagneet wrote:
Hi Oleg,
Thanks for your inputs. Now I am making a new HttpState object for each request made. But have found a new problem. This problem occurs when the requests are concurrent. What is evident is that after redirection happens the JSESSIONID of both the requests become
@hc.apache.org
Sent: Thursday, April 03, 2008 12:14 AM
Subject: Re: Problem sending request using HttpClient when the server
receiving request goes down and is started again.
gagneet wrote:
Hi Oleg,
Thanks for your inputs. Now I am making a new HttpState object for
each request made
Hi Oleg,
As I was using Singleton HttpClient object the JSESSIONID persisted for every
request. I have cleared the persistence by calling clearCookies() method on the
HttpState object corresponding to the HttpClient object. Should I call this
method after every call or should I call it only
Hi Oleg,
I guess you missed my last post or may be I was not very clear. I have
noticed that recreating an instance of HttpClient solves the problem. But then
is it advisable to create a new instance of HttpClient in an application when
same url is to be hit? The problem is that
Hi All,
I am facing a problem using HttpClient (version 3.0-rc3) while sending a
request(from WebSphere Portal Server 5.1.1.10 which is using JDK1.4.2) to a
HttpServer. When the HttpServer is up then there is no problem as such. When I
stop that server and make a request I get Operation timed
