Hi there,
I'm using HttpClient 2.0.2 and noticing that in a particular use case,
SSL sockets are staying in CLOSE_WAIT forever (overnight so far), with
one byte in Recv-Q. A customer has reported "Too many open files."
We've increased their ulimit from 1024 to 10240 open files, but this is
only a temporary solution.
We're calling releaseConnection() after each request, and the
MultithreadedHttpConnectionManager only ever has one connection in its
pool. I've noticed that HttpConnection.closeSocketAndStreams() is
called regularly for our non-SSL sockets, which also use
MultithreadedHttpConnectionManager, but never for our SSL sockets.
Note that we do use a wrapped HostConfig in order to override the JDK's
TrustManager, but the SocketFactory implementation itself is the one
that comes directly from SSLContext.
Will upgrading to 3.0 solve this problem? And if so, is anyone aware of
any important non-default settings in 3.0 that are different from 2.0.2?
Thanks,
-0xe1a
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
