Hi Mauro, The Query Compilation Cache is ON by default. You don't have to do anything with this. I was just pointing out the functionality.
Since you are using the OpenJPA 1.1.x branch, I'm going to copy the owner of that branch on the chance that there's something already known in this area. Like I mentioned in the previous reply, maybe there's something in the app server (WebLogic in this case) that is not cleaning up the EntityManagers appropriately. It sounds and looks like you have a fairly straight-forward configuration, so hopefully we'll get a reply from someone more familiar with the 1.1.x branch. Kevin On Tue, May 26, 2009 at 4:44 PM, Mauro Flores < [email protected]> wrote: > > I'm not using so far any custom openjpa property like 'Query Compilation > Cache'. I'll try to use some of them. > > My scenario is this: > > application server: weblogic 10.3 > version kodo: 1.0.0.0_4-2-0 > version openjpa: 1.1.0 > > Persistence XML > > <?xml version="1.0" encoding="UTF-8"?> > <persistence xmlns="http://java.sun.com/xml/ns/persistence"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://java.sun.com/xml/ns/persistence > http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"; > version="1.0"> > <persistence-unit name="CAF"> > > <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider> > <jta-data-source>CafDS</jta-data-source> > <mapping-file>META-INF/orm.xml</mapping-file> > <class>...</class> > </persistence-unit> > </persistence> > > Thanks! > -- > View this message in context: > http://n2.nabble.com/Memory-Leak-and-JJCalls-tp2971921p2977452.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > >
