Hi Eric, I didn't dive into the code, so you're probably right. It would make sense for a single thread scenario not to block, even though the connection was not released. I must admit that I didn't even consider the possibility of a manager, no matter how simple, that allows multiple allocation of a single resource :-)
Then maybe he does use the MultiThreadedHCM and the first few requests succeed before the pool is exhausted. cheers, Roland Eric Johnson <[EMAIL PROTECTED]> 07.09.2004 19:15 Please respond to "Commons HttpClient Project" To Commons HttpClient Project <[EMAIL PROTECTED]> cc Subject Re: URLGetMethod.executeMethod is hanging under multi threaded environment Roland Weber wrote: [snip] >With your implementation and the SimpleHttpConnectionManager which is >used by default, a single download should succeed. All other downloads >then wait for the connection that is never released by the first one. > > > Did this change? Last time I checked, I thought that the SimpleHttpConnectionManager would explicitly complete the processing of the previous response when a new request was issued, rather than blocking waiting for the previous one to complete. -Eric. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
