DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23703>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23703

Freezes w/ MultiThreadedHttpConnectionManager





------- Additional Comments From [EMAIL PROTECTED]  2003-10-10 16:33 -------
I have 'longstanding issues' w/ this stack also, having VFS between my code and 
yours causes me grief (since sadly VFS isn't too active these days.) Ruper2 
started in part to make VFS 'optional' (which was not possible in Ruper1). 
Yesterday I completed that endeavor, and now I have a direct interface to 
HttpClient for what I need. 

I followed your samples, and advice, and it is solid ... no connection leaks in 
user code. I will post the code, so you can see it, there is very little code.

In short, I get the same problem w/ no possible confusion. It isn't a "simple 
test harness" (sorry) but it is a clean user -- and it demonstrates the problem 
in even during a "clean run" -- i.e. no server/network errors, against normal 
servers, etc. If I make my code avoid the multi threaded connection manager it 
works correctly. 

I want to stick against HEAD in part so I help you guys test this, in part 'cos 
Ruper is about keeping up w/ latest Jars, and in part 'cos I ahbor Jar Hell 
(http://www.krysalis.org/version/jar-hell.html)

I am game to work w/ you guys to fix this, if you are. I fear that multi-
threaded connection pool management it tricky (at best), especially when users 
can mess up the pool. So (if you have time) maybe this is worth exploring. 
Perhaps we could add some better debug/trace & keep trying?  Perhaps I could 
get you hooked up w/ Ruper2 code, for you to run in a debugger. Your call.

regards

Adam

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

Reply via email to