Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
Date: Thu, 12 Jul 2001 08:31:45 +0200 (MET DST)
From: =?iso-8859-1?Q?Endre_St=F8lsvik?= <Endre@Stolsvik.com>
To: <tomcat-user@jakarta.apache.org>,
	Boris Niyazov <niyazov@solni.law.columbia.edu>
Subject: Re: Tomcat memory-leak problem
In-Reply-To: <200107112125.RAA28781@solni.law.columbia.edu>
Message-ID: <Pine.GSO.4.33.0107120829210.22294-100000@jeeves.stud.ntnu.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 11 Jul 2001, Boris Niyazov wrote:

| You should probably look at your code for possible memoey leaks: not closed db
| objects (statements, result sets, connections) not closed file descriptors, etc.

More important, I think, is stuff you shove inside Collections.

The RS'es, Files and all that stuff will eventually be GC'ed when they go
out of scope, that is, no reference is left for them. (IF they do, of
course).

Only way to have leaks in Java is to make objects that are in your
"working set" (reachable set) of objects and that never goes out of scope.
--> Like some caching mechanism where the only thing you do is to _add_
objects to the cache, and never release them.

-- 
Mvh,
Endre