On 07/02/2001 at 11:05:09 AM, owner-java400-l@midrange.com wrote:
Fred, I thought that GC also removes objects which
have no references (i.e. unreachable ?) So, if your
statement objects/result set objects do not have a
reference (beause the connection pool has been pushed
back to the con pool), they ideally need to be GC'd -
Am I right ?
--- end of excerpt ---
What Rich said. 8-)
I.e. yes, the GC removes unreachable references, but only
based on its decisions related to storage utilization, and
only when it needs to.
Further more, Most JDBC drivers maintain references to those
objects internally, so technically they are NOT unreachable.
(i.e. Connection refers to statement objects, while Statement
objects refer to ResultSet objects).
Rich has ensured that our native JDBC driver uses weak references
where it makes sense so as to enable the GC a little more,
but you cannot depend on this from a JDBC portability perspective.
You must use the close() method.
Especially in a mission critical 'always on' application.
"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
+---
