Hello All,
Is there is a direct way to control the maximum no of threads in waiting for
a connection from the Connection Manager.
Thanks in advance for your openion.
--Satya
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
I am using the following code:
HttpClient client = new HttpClient(connMgr);
client.setHostConfiguration(hostConfig);
PostMethod method = new PostMethod(tokenURL);
method.setQueryString( userModel.getQueryString() );
client.executeMethod(method);
byte[] responseBody = method.getResponseBody();
Hello Mike,
getConnectionsInPool() is certainly a more intutive name.
At the same, as you already mentioned, certainly there need to be a
connection killer method:
MultiThreadedHttpConnectionManager.destroyIdleConnections(long idleTime)
Also, I would recommend one method which could spit o
After Calling
MultiThreadedHttpConnectionManager.closeIdleConnections(idleTime), the
timedout connections are closed, however, connectinon count does not
decrease.
Therefore, if I call
MultiThreadedHttpConnectionManager.getConnectionsInUse(), I still get the
same value as before calling close
I was wondering why this method was depricated, currently I use:
MultiThreadedHttpConnectionManager.getParams().setIntParameter("http.connect
ion-manager.max-per-host",20);
Which fairly un-intutive, as compared to the earlier method
setMaxConnectionsPerHost(20), which is depricated now.
Any
