Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <758292707.1257522632400.JavaMail.jira@brutus>
Date: Fri, 6 Nov 2009 15:50:32 +0000 (UTC)
From: "Albert Lee (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Resolved: (OPENJPA-1375) OutOfMemory runs in container
 environment in a long stress run
In-Reply-To: <1145020132.1257371852411.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Albert Lee resolved OPENJPA-1375.
---------------------------------

    Resolution: Fixed

> OutOfMemory runs in container environment in a long stress run
> --------------------------------------------------------------
>
>                 Key: OPENJPA-1375
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1375
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.3.0, 2.0.0-M3
>            Reporter: Albert Lee
>            Assignee: Albert Lee
>             Fix For: 1.3.0, 2.0.0
>
>
> Long stress run in the app server/container environment caused a OutOfMemoery exception with a heap dump that showed the following:
>  FetchConfigurationImpl$ConfigurationState
>  + WsJpaFetchConfigurationImpl
>     + Array of Object
>        + IdentityHashMap
>           + EntityManagerImpl
> What happened is the container pooled the entity manager and clear the context when a transaction is completed. However the IdentityHashMap in EntityManagerImpl, which maps the fetch configuration to fetch plan, is not being flush/clear. This caused the growth of the IdentityHashMap and eventually the OOM in a long run.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.