Re: Java Exception in JDBCR4

On 1/21/2014 4:02 PM, Scott Klement wrote:

You are running out of memory. I think it's just 'chance' that this
occurs on the 'close' -- it could potentially occur anywhere.

Make sure you are cleaning up after yourself (calling the various 'free'
functions as needed). If this is still happening, consider increasing
the amount of memory available to the JVM.

As an RPG programmer, I rarely (if ever) think about returning memory
back to the system. Automatic storage, the heap and static storage seem
so... theoretical until we get into the static keyword on the
d-specifications.

The rest of the programming world isn't so lucky. Java grabs memory
from the system and doesn't give it back until we tell Java that we're
done with it. It's pretty easy for a Java newbie (raises hand) to
exhaust memory. So the first half of Scott's advice is very important
to bear in mind.

Aside from not freeing up memory that's no longer needed, there is
another possibility: You might actually be using all that memory
intentionally. I routinely run out of memory when I'm trying to build a
spreadsheet with say half a million rows. Not because I forgot to free
things up, but because such a large spreadsheet takes up a lot of room -
more than the JVM is configured for. That's where the second half of
Scott's advice comes into play.
--buck