Jan,
Good point. With Java you don't have to remember as much about silly things like 
malloc and free in C/C++ which led to all sorts of problems.
 
However, you do have to worry about GC, object creation and holding on to objects for 
too long. 
 
Something like HPJMeter may help in analyzing the problem:
http://www.hp.com/products1/unix/java/developers/hpjmeter.html
 
Mark
 
 

        -----Original Message----- 
        From: Jan Gonsalves [mailto:[EMAIL PROTECTED] 
        Sent: Thu 5/29/2003 6:09 PM 
        To: Commons HttpClient Project 
        Cc: 
        Subject: Java can leak...
        
        

        Oleg,
        
        I understand what you mean my mem alloc, but Java can leak, it's a
        proven fact.  Anytime ROOT has a reference to something it makes it
        unable to GC, however, if you loose your reference and ROOT still has
        it's, that's a memory leak.  ROOT will never GC that memory.  Ask
        youself this, if Memory leaks were impossible in JAVA, how can programs
        such as JProfiler or OptimizIt sell?
        
        Jan
        
        Oleg Kalnichevski wrote:
        
        >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]
        >
        >
        > 
        >
        
        
        ---------------------------------------------------------------------
        To unsubscribe, e-mail: [EMAIL PROTECTED]
        For additional commands, e-mail: [EMAIL PROTECTED]
        
        

Reply via email to