Arul Govindarajan wrote:
Thanks for the response. The fact that the siteminder token( for SSO) in the
cookie is not getting accepted, the request gets forwarded to a login
page(which is HTTPS) and that explains the SSL Handshake exception.
If the problem is then because the reused connections retain some of the data
from previous requests, do you know if there are any ways to clean up before
making a new request?
Arul,
HTTP connections are usually stateless. However they may become
stateful, if used within a particular security context. For instance,
NTLM authenticated connections are stateful, as they carry information
about user's identity, so can be SSL connections if their SSL context
carry some state information (user principal or a SSL session id
associated with a particular security context)
This kind of state cannot be cleared. HttpClient 3.1 can't handle
stateful connections at all. HttpClient 4.0 can. The only option you
have if you want to continue using HttpClient 3.1 is force the
connection manager to close all connections released back to the pool.
Hope this helps
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
