Setting QueryCache to false did not seem to affect the bahviour - still same memory usage. Should I provide the heap dump as well for this one?
DataCache show through jmx beans rather light usage too. But maybe the links are hidden somehow via the LRS proxies - cache holds owner of LRS entities that we iterate on (Run and Catalog) One thing I noticed that surprised me is that for composite Ids, the Id derived from the parent class is always a new instance even it identifies the same instance, i.e. RunId is part of SourceResultId and even with identical values of RunId - SourceResultsIds have separate RunIds created instead of referencing the same one. But this is irrelevant here of course. Thanks, Chris -- View this message in context: http://openjpa.208410.n2.nabble.com/Memory-leak-for-long-lived-read-only-EM-tp7581554p7581566.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
