Thanks for the suggestions thus far. I ran a little
test and created a loop that tried to save class A in the database 10000 times. It only got to 893 when it ran out of memory too. So I conclude that it's somewhere in my
jdbc stuff. Should this be moved to that forum?
Anyway, here is the method being called many times:
It calls some methods in the Position class which is really just a class representing a row of data in a database. The culprits are the methods that do sql so we can focus on the store(count) method, which is listed below:
The DBConnection.getConnection() is a simple connection pooling class I've developed that just grabs existing database connections and then let's you return them to the queue when you're done with them.
ms