Jan, HttpClient is a pure Java application and as such does not manage memory allocation directly. I suggest that you check if there are any known issues with the jvm you are using. Upgrading to HttpClient beta-1 would not hurt, anyways.
Oleg On Thu, 2003-05-29 at 16:36, Jan Gonsalves wrote: > Does anyone know of any memory issues with opening a connection and > continuely re-using it, only closing it when a socket timeout happens? > I'm currently using ALPHA 3. I have to "fake out a browser" and > navigate through a website to extract information because they don't > offer a straight DB connection. I re-use this connection the whole > time, never closing it, only recycling it, unless I get a socket > timeout, ConnectionException, or HTTPRecoverableException. Our > Production server has 4GB of ram. Last night we ran and the system went > down to 4MB free, 4! I'm just wondering if I'm leaking due to HTTP > Client. I've gone over my stuff and it looks relatively solid, I'm > wondering now if I'm using HttpClient incorrectly. Does Beta 1 help > with any memory issues? > > Jan Gonsalves > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
