of a HttpConnectionManager.
Either a SimpleHttpConnectionManager or a
MultiThreadedHttpConnectionManager depending on your circumstances.
Mike
On Monday, August 11, 2003, at 05:13 PM, David Wade wrote:
> Oleg,
>
> I tried testing on my home x86 Linux box under IBM1.4.1 and Sun1.4.2
> and
> moni
Of course I meant getResponseAsStream not getResponseBodyAsStream
-Original Message-
From: David Wade [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2003 10:10 a.m.
To: 'Commons HttpClient Project'
Subject: RE: getMethod.getResponseBody() leaks handles
Mike,
Than
ute any of clean up code, that happens in the second example.
Obviously I have a workaround, but feedback on whether other have the same
result (on Solaris would be interesting).
Ta.
____
David Wade Senior Consultant
Opti
Mike,
thanks for the detailed reply, but sorry if try one more
time to force my point of view ;>
I just don't get why the behaviour should be different.
My perspective on this is from a users view of the client
and form that perspective it doesn't make sense for the
different behaviour and t
Mike,
Just ran my leaky program with a breakpoint
in HttpMethodBase.responseBodyConsumed(). I can categorically
tell you it is not called!
David
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 12 August 2003 1:36 p.m.
To: Commons HttpClient Project
Subj
Oleg, Roland,
I tried to reproduce that last night (I'm on GMT+12) but failed, probably
from going round too many circles and don't have a snapshot of the code when
(I think) it happened. Perhaps we have got away from the original issue
that calling getResponseBody() and calling getResponseBodyAs
pment branch of HttpClient
is no longer completely 2.0 API compatible. Some minor tweaks to your code
may be necessary.
http://cvs.apache.org/builds/jakarta-commons/nightly/commons-httpclient/
Cheers
Oleg
-Original Message-----
From: David Wade [mailto:[EMAIL PROTECTED]
Sent: Monday, August