[jira] Created: (OPENJPA-1375) OutOfMemory runs in container environment in a long stress run

4 messages Options
Embed this post
Permalink
JIRA jira@apache.org

[jira] Created: (OPENJPA-1375) OutOfMemory runs in container environment in a long stress run

Reply Threaded More More options
Print post
Permalink
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: 2.0.0-M3
            Reporter: Albert Lee
            Assignee: Albert Lee
             Fix For: 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.

JIRA jira@apache.org

[jira] Updated: (OPENJPA-1375) OutOfMemory runs in container environment in a long stress run

Reply Threaded More More options
Print post
Permalink

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

Albert Lee updated OPENJPA-1375:
--------------------------------

    Affects Version/s: 1.3.0
        Fix Version/s: 1.3.0

> 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.

JIRA jira@apache.org

[jira] Closed: (OPENJPA-1375) OutOfMemory runs in container environment in a long stress run

Reply Threaded More More options
Print post
Permalink
In reply to this post by JIRA jira@apache.org

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

Albert Lee closed OPENJPA-1375.
-------------------------------


> 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.

JIRA jira@apache.org

[jira] Resolved: (OPENJPA-1375) OutOfMemory runs in container environment in a long stress run

Reply Threaded More More options
Print post
Permalink
In reply to this post by JIRA jira@apache.org

     [ 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.