Hi, 1. JProfiler documentation provides useful guidelines to ascertain a memory leak and narrow its source [1]. Some of these guidelines may help to identify the cause. Our first (and possibly misguided) assumption was PCRegistry -- but double-checking that assumption is required.
2. why does java.beans.BeanInfo appear in the memory heap profile? OpenJPA configuration elements implement BeanInfo interface, but the presented memory profile is about the persistent classes. Is any of the entities implementing/using BeanInfo? 3. Can it be something specific to the data itself? You mentioned eager fetching of one-to-many relation from BaseContent to RepeatedAttribute and eager? Can cardinality of that relation grow huge under long running operations? 4. Somewhat off topic: you mentioned that the sessions are read-only. How is the application taking advantage of that fact. [1] http://resources.ej-technologies.com/jprofiler/help/doc/helptopics/memory/memoryLeak.html Darren Senel wrote: > > Good morning Pinaki, > > So our site spider had the effect we were looking for and out of our three > servers 1 crashed with an OOM, the other two survived but heap usage is > around 95% on them! I ran the debug code on these two servers and the > results are that there was only 13 persistent classes listed with the same > classloader. > > Here is the output from server for your validation: > > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.BaseContentDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.lists.RepeatedAttribute loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.DynamicCollectionDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.PrimaryContentDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.FriendlyURLDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.translations.TranslationDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.translations.VTranslationDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.ConfigDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.MigrationMasterDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.translations.SubgroupDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:523 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.translations.GroupDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:538 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.taxonomy.TaxonomyDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > [6/30/09 8:06:52:538 EDT] 000022f1 SystemOut O > com.pwc.us.wcps.dto.TerritoryDTO loaded with classloader: > com.ibm.ws.classloader.compoundclassloa...@714a714a > Delegation Mode: PARENT_LAST > > I am assuming now we have to look at an alternative root cause? > > Any ideas where to start looking? > > Cheers > > Darren > > > Darren Senel wrote: >> >> Hi Pinaki, >> >> I can output the debug lines on demand, so I will wait until memory is >> constrained and issue the command. I'll let you know if there are more >> than 13 persistent classes registered and if there are more than one >> classloader displayed. >> >> We have a bot spider the site at around 5:00pm today, which expedites the >> issue, so I should be able to let you know later today or tomorrow the >> results of this test. >> >> Cheers >> >> Darren >> > > ----- Pinaki -- View this message in context: http://n2.nabble.com/Memory-Usage-tp3166851p3183133.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
