This data structure is what is normally returned when executing Query.getResultList(). I agree that your png shows a large ResultList. But, I would question what type of query and what type of object model is being used to populate such a large result. Are all of your relationships set to Eager fetch mode? Or, does your query span thousands of rows of data? Maybe you should consider Large Result Set processing [1]? This would help with only getting chunks of the requested data at a time, instead of everything all at once.
At this point, I wouldn't call this a memory leak. I would just call this a huge consumer of memory. I mean, this data structure isn't growing, is it? It's just a very large ResultList, right? Good luck, Kevin [1] http://ci.apache.org/projects/openjpa/trunk/docbook/manual.html#ref_guide_dbsetup_lrs On Fri, Apr 25, 2014 at 9:07 AM, pbt123 <[email protected]> wrote: > Can anyone give some clue/reason on the memory leak in my application? > > Leak suspect is: org.apache.openjpa.lib.rop.EagerResultList > > > <http://openjpa.208410.n2.nabble.com/file/n7586286/MemoryLeak.png> > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Memory-Leak-tp7586286.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. >
