Re: releasing streamed connections back to connection pool

I think I've found the problem. The Spring code isn't closing the input stream from the response after reading it. Easy to override and fix. Thanks for your help... On Fri, Apr 8, 2016 at 11:10 AM, Tim Webster wrote: > Hi sorry I'm not sure which question you are

Re: releasing streamed connections back to connection pool

Hi sorry I'm not sure which question you are answering, but it sounds like you are saying that as long as I consume the response properly then the connections should be re-used properly (and not closed), despite the call to releaseConnection()? If that is so, why do we need the call to

Re: releasing streamed connections back to connection pool

OK...so do you think I need to use this class to explicitly to consume the response? I can see some methods on there for this. Also - I think the call to PostMethod.releaseConnection() will still close it - do you have any idea if this should / should not be used? Thanks, On Fri, Apr 8,