× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I thought JAVA has a garbage collector making memory leaks a thing of the past. So that once the variable goes out of scope or if you explicitly set it to null the garbage collector will release that memory. Same thing happens in .NET...

-----Original Message-----
From: James H. H. Lampert [mailto:jamesl@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, November 20, 2013 7:03 PM
To: Midrange Systems Technical Discussion
Subject: Just realized that I probably have another memory leak in RPG calling Java

In my JDBCR4-based project, I'm calling JDBC_GetMetaData (which front-ends ResultSet.getMetaData(), and returns a ResultSetMetaData object).

But I just realized that I'm not getting rid of the ResultSetMetaData before getting one on another ResultSet.

And I've also front-ended Connection.getMetaData(), which returns a DataBaseMetaData object, and there, too, I'm not getting rid of one before getting another.

I'm having a major brain-fart about how to fix this.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.