Well, GC releases memory used by JVM, but statements and RS can be unrelesed on
the db level (depending on db engine), so if your db resides on the same box
then eventually you gonna have memory problems on the box.
- Boris
>
>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
>
