Kim B. Andersen wrote:
httpclient client = new hhtpClient(); method = new getMethod(url); client.execute(method); ... ... method.releaseconnection();
Please put a finally clause around releaseConnection, just to make sure it is called even when an exception occurs.
How can I see if the pool is empty?
If you get a line in the log like: Unable to get a connection, waiting... then the pool is empty.
* Maybe attach a debugger / profiler or use jconsole I have never played with these tools so I don't no how at the moment. I will try to look into it, but if you can recommend some website to read or describe how to - I would appreciated alot.
Sorry, we are not offering free online courses in software engineering. Please use other resources.
First hour 2006/01/03 14:46:49:926 CET [DEBUG] HttpConnection - Open connection to fastnetselvbetjening.tdconline.dk:443 2006/01/03 14:46:50:038 CET [DEBUG] header - >> "GET /Krump/Alivetest.do?ws HTTP/1.1[\r][\n]"
After the first hour 2006/01/04 07:58:50:230 CET [DEBUG] HttpConnection - Open connection to fastnetselvbetjening.tdconline.dk:443 2006/01/04 07:58:59:230 CET [DEBUG] header - >> "GET /Krump/Alivetest/alivetester1.html HTTP/1.1[\r][\n]"
That's definitely helpful. The connection pool is apparently NOT the problem. But it takes longer when actually opening the connection. As to why that happens I can only speculate. Do you have control over the target host? Is it possible that they perform some dynamic connection rate limiting?
Cheers Ortwin Glück --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
