Re: JDBC Connection Pooling

On 06/29/2001 at 03:04:01 PM, owner-java400-l@midrange.com wrote:
This has hit me hard in the past and found it out the hard way
because the jdk1.1.8 was not efficient on garbage
collection. What is your jdk level.
--- end of excerpt ---

Bad idea, focusing on the GC for this particular question...
It doesn't necessarily reflect a problem in the GC.
Although you may be correct about weaknesses in
GC, this is certainly a bug on behalf of the _application_ anyway.
You can't rely on the garbage collector to cleanup any resources
other than storage.

The garbage collector only runs when memory gets low.
It knows nothing about other resources high/low water marks
or what resouces may be allocated other than storage.
I.e. Depending on the size of your heap, you may have
megs and megs and megs of storage left even though you
leaked thousands of statements/result sets.

The garbage collector only collects based on decisions
about memory utilization.


"The stuff we call "software" is not like anything that human society
  is used to thinking about. Software is something like a machine, and
  something like mathematics, and something like language, and
  something like thought, and art, and information...
  but software is not in fact any of those other things."
Bruce Sterling - The Hacker Crackdown

Fred A. Kulack  -  AS/400e  Java and Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN  (Phone: 507.253.5982   T/L 553-5982)
mailto:kulack@us.ibm.com   Personal: mailto:kulack@bresnanlink.net
AOL Instant Messenger: Home:FKulack  Work:FKulackWrk

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---