Nightmare java leak… with loop and jdbc

Question

When I run the following code in the profiler, I get a char[] and byte[] that build up until the program crashes due to a java heap out of memory exception. Can someone tell me

Answer 1

I would change this:

                        statement.executeQuery(rawQuery);
                        results = statement.getResultSet();

to this:

                        results = statement.executeQuery(rawQuery);

The latter is certainly the API-approved way to do this, and while I can't say for certain that the former is a problem, it certainly seems like it could create two separate result-sets, of which you only close one.