I got rid of the call explicitly freeing the DBMD . . . and it turns out
it's still crashing. This time it crashes ON the call freeing the
ResultSetMetaData.
Near as I can tell, at this point, the ResultSet on which I got the RSMD
was freed earlier, but the RSMD was still there for inspection (at least
in a test I ran yesterday), yet evidently can't be explicitly freed
without crashing the JVM. And yet if I take out the explicit free of the
RSMD, it works, and the "new" RSMD is definitely a different object from
the old RSMD.
Would a series of Java dumps on my job tell me anything about whether
the apparent memory leaks from failing to explicitly release my meta
data objects is real or illusory?
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
