Hello Ash,

> I have created HttpClient as a singleton, using the
> MultiThreadedHttpConnectionManager connection manager as suggested on
> the threading section of the apache site.  

What are the limits for max connections and connections per host
on the manager?

> In the code that posts the soap message to the secure server: -
> 
> - get an instance of the HttpClient

"an instance"? You mean "the instance", right? Otherwise there
is something wrong with your singleton implementation :-)

> - create the PostMethod
> - use post.setRequestEntity to set the Soap message to be sent
> - set timeouts on the connection manager

What for? If you want timeouts to take effect for the method
execution, set them in the method params. If you want the
same timeouts for all method executions, set them in the
default params for the HttpClient. See the preferences guide:
http://jakarta.apache.org/commons/httpclient/preference-api.html

> - execute the Post Method
> - get the response body
>
> In the finally I do a post.releaseConnection();

releaseConnection will give the connection back to the pool,
but does not close it. Anyway, the number of connections is
limited by the pool, so that should not be a problem.

> All is well when I put a medium amount of load through it the amount of
> files stay at a reasonable size (monitored by pfiles on unix), but if I
> put a lot of traffic (twice the amount) it quickly increases to above
> the 1024 limit and doesn't seem to recover until I restart the managed
> server.
> 
> This is on WLS 8.1 SP4 on Solaris 9 using the 3.0.1 release of Apache
> Client.
> 
> Does anyone have any ideas of why this could be happening and any ideas
> on how to fix it?

Are there any known problems with your SSL implementation?
Some of them are broken pretty badly, I have heard.

Are you sure that there is no file handle leak somewhere else
in your code?

cheers,
  Roland

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to