Hi Darren, This is usually happens if the application creates a large number of EntityManager*Factories*, which aren't closed. Take a look at the application logic where you obtain the EMF, and make sure it gets closed (or cached appropriately).
hope this helps, -mike On Sat, Jun 27, 2009 at 10:54 AM, Darren Senel <[email protected]>wrote: > > Hello, > > We are using OpenJPA 1.2.0 in a WebSphere 6 web application. We are not > using the EJB3 pack. We are seeing a very large proportion of the heap > taken up by OpenJPA PCRegistry objects (as shown in image). We use compile > time enhancement of our classes. Eventually with enough requests of under > high load our servers fail with an OOM error as the heap is exhausted. The > image below shows the heap analysis suspected leak subject. Also, this > heap > dump was taken when the heap was about 50% full. > > We open, use, flush, close and set to null the EntityManager objects we > create. > > Would anyone have any ideas as to the cause of this growth of objects that > eventually leads to our OOM crash? > > Many thanks, > > Darren > > http://n2.nabble.com/file/n3166851/HeapAnalysis.jpg > -- > View this message in context: > http://n2.nabble.com/Memory-Usage-tp3166851p3166851.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > >
