Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of curtisr7@gmail.com designates
 209.85.217.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=AYmIGvaNgFv7taDz4pn6tsxFXVZym/qFshseiQLIOF0ldBCOXUbP8kfTkgsLjSweag
         J4giggKBzv77Czs9zezp+oxQF0VVZdeqzk/8eyLWKgzKRoJEiQ1QXrQCpe/WvzYwyNkO
         oYKabHiBk+jxbqEkJeff7TiuoMQyNLalpYShE=
MIME-Version: 1.0
In-Reply-To: <AACE232EE570F846A6499C6A4C93EC75F4C954@exchange.d-velop.de>
References: <AACE232EE570F846A6499C6A4C93EC75F4C954@exchange.d-velop.de>
Date: Tue, 25 Aug 2009 10:16:39 -0500
Message-ID: <f8b633140908250816s72fc7e9and93ba60d2105f210@mail.gmail.com>
Subject: Re: Memory Issues
From: Rick Curtis <curtisr7@gmail.com>
To: users@openjpa.apache.org
Content-Type: multipart/alternative; boundary=000e0cd5f6663461120471f8d215

--000e0cd5f6663461120471f8d215
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Kevin -

I'm willing to bet that the problem you're running into is a result of not
enhancing your Entities. Take a read through the 'Entity Enhancement' page
[1] and let us know how it goes.

Thanks,
Rick

[1] http://openjpa.apache.org/entity-enhancement.html

On Tue, Aug 25, 2009 at 9:24 AM, Lohmann Kevin <kevin.lohmann@d-velop.de>wrote:

> Hi *,
>
> I'm using openjpa 1.2.1 and Derby 10.4.2.0 and I'm getting
> OutOfMemoryErrors (Java heap space).
>
> I have a class named 'Data' which has a byte-array. The class is
> annotated.
>
> In a small test I create one EntityManagerFactory and - in a loop - 100
> EntiyManagers.
>
> For each EM I start a transaction, create a Data-Object, fill it with
> the byte-array, persist the object, commit the transaction and close the
> EM.
>
> Surprisingly the OutOfMemoryError occurs after the ~70. loop-event. With
> JProfiler I see, that all Data-Objects are still in the memory, but I
> don't use any cache (DataCache + QueryCache). The objects are held by
> 'org.apache.openjpa.enhance.ReflectingPersistenceCapable' and
> 'org.apache.openjpa.lib.util.concurrent.ConcurrentReferenceHashMap'.
>
> Is it because I use RuntimeEnhancement?
>
> I guess, I miss some configuration!? With Hibernate or EclipseLink these
> OOME doesn't occure (the objects are then gc'ed - just like expected!).
>
> Can anyone point me to the missing config parameter? Or is it a known
> bug, which I can find in the inet?
>
> The config-parameter I use:
>
>        props.put("openjpa.ConnectionURL",
> "jdbc:derby:C:\\database";create=true");
>        props.put("openjpa.ConnectionDriverName",
> "org.apache.derby.jdbc.EmbeddedDriver");
>
>        props.put("openjpa.jdbc.SynchronizeMappings", "buildSchema");
>        props.put("openjpa.RuntimeUnenhancedClasses", "supported");
>        props.put("openjpa.MetaDataFactory",
> "jpa(Types=\"use.database.Data\")");
>
>        props.put("openjpa.Multithreaded", "true");
>
>        props.put("openjpa.Log", "log4j");
>        props.put("openjpa.ConnectionFactoryProperties",
> "PrettyPrint=true, PrettyPrintLineLength=22");
>
>        props.put("openjpa.DataCache", "false");
>        props.put("openjpa.QueryCache", "false");
>
> My Code:
>
>        EntityManagerFactory lEMF = Persistence
>                                .createEntityManagerFactory("openjpa",
> props);
>
>        for (int i = 0; i < 100; i++) {
>
>                EntityManager lEM = lEMF.createEntityManager();
>
>                lEM.getTransaction().begin();
>
>                Data lData = new Data();
>                // Here a file is read out, that has a size of 800kb
>                lData.setContent(getContentFromFile());
>
>                lEM.persist(lData);
>                lEM.getTransaction().commit();
>
>                lEM.close();
>
>        }
>
> Cheers,
>  Kevin
>

--000e0cd5f6663461120471f8d215--