Using memory analyzer tools ( like eclipse mat) you can get incoming and outgoing references to the suspected object. You can collect these stack traces and that may help to narrow down the issue.
Regards, Ravi. -----Original Message----- From: Michael Dick [mailto:[email protected]] Sent: Friday, September 10, 2010 2:48 PM To: [email protected] Subject: Re: JPA - PCRegistry consuming 80% of Java heap - Production Error - Help! Just a FYI, you might need some help from WebLogic support on this issue. Most of the people on this list have little / no awareness of the Kodo code base. Kodo probably isn't causing this problem - but it can interact with OpenJPA in unexpected ways. That sadi, you might be hitting OPENJPA-1670<https://issues.apache.org/jira/browse/OPENJPA-1670>. The PCRegistry contains two collections : a list of RegisteredClassListeners, and a map of Class -> ClassMetaDatas. You probably want to inspect the heap and see which objects in PCRegistry are taking up space. If it's RegisteredClassListeners, then OPENJPA-1670 should fix it. If it's classes or ClassMetaDatas then it's a different problem. Hope this helps, -mike On Fri, Sep 10, 2010 at 3:34 PM, Kwi De Silva <[email protected]> wrote: > We have a J2EE App running in Weblogic 10.3 and are receiving > OutOfMemoryException's. A dump of the heap shows that > org.apache.openjpa.enhance.PCRegistry is taking up 79.91% of the heap > (see below). > > Class Name | Shallow Heap | Retained Heap | Percentage > > --------------------------------------------------------------------------------------------------- > class org.apache.openjpa.enhance.PCRegistry | 16 | > 234,453,760 | 79.91% > > --------------------------------------------------------------------------------------------------- > > JVM Params are listed below > > -Xms1024m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m > -Dweblogic.Domain=mydomain -Djava.awt.headless=true -Duser.language=en > -Duser.region=US -Dweblogic.Environment=prod > > We are using OpenJPA shipped with WL10.3, the name of the JAR file is > org.apache.openjpa_2.2.0.0_1-1-0.jar. > > The JPA Runtime appears to be using BEA Kodo 4.2.0load03 > > Has anyone ANY idea what is going on here. The server runs out of > memory after a week or 2, and needs to be recycled. > > Any help greatly appreciated :-( >
