executeMethod(method);
// System.gc();
// method.releaseConnection();
}
}
Uncommenting either of the last two lines makes the problem go away...
- Original Message -
From: "Michael Becke" <[EMAIL PROTECTED]>
To: "Commons HttpClient
> Yes, but you have done a very bad thing here. By doing the
> executeMethod(), you have established a connection to the server, and
> have read the headers. But then you are closing the connection before
> reading the body. The client (thats you!) is responsible for completing
> the read by
ll a handle on the method at this point, and the connection
is still in use so neither are elligible for garbage collection ...
Jandalf.
- Original Message -
From: "Michael Becke" <[EMAIL PROTECTED]>
To: "Commons HttpClient Project" <[EMAIL PROTECTED]>
S
;Commons HttpClient Project" <[EMAIL PROTECTED]>
Sent: Sunday, February 02, 2003 6:18 AM
Subject: Re: Running out of connections
> Hello Simon,
>
> Sorry to be replying so late. Connections are released when:
>
> 1) the response is fully read
> 2) the connection i
not freed!
Shouldn't we expire them if we're running out of connections?
Cheers, Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
) and the reply include a "Connection: close". If no garbage-collect happens then the connections are not freed!
Shouldn't we expire them if we're running out of connections?
Cheers, Simon
-
To unsubsc
Shouldn't we expire them if we're running out of connections?
>
> Cheers, Simon
--
Oleg Kalnichevski <[EMAIL PROTECTED]>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ns are not freed!
Shouldn't we expire them if we're running out of connections?
Cheers, Simon
