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 JSESSIONID remains in the earlier
HttpClient object. Probably JSESSIONID is created because of automatic cookie
handling in HttpClient. Is there a way to refresh the HttpClient object i.e. to
clear whatever is stored in it?
Regards,
Gagneet
---------------------------------
Unlimited freedom, unlimited storage. Get it now
