Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <25790055.1247081354787.JavaMail.jira@brutus>
Date: Wed, 8 Jul 2009 12:29:14 -0700 (PDT)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Closed: (OPENJPA-1161) Identified MemoryLeak in
 MappingRepository
In-Reply-To: <1335780766.1246994535133.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-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick closed OPENJPA-1161.
---------------------------------

    Resolution: Invalid

Based on Brian's info this sounds like a WebSphere issue, I'm tentatively closing the JIRA. 

> Identified MemoryLeak in MappingRepository
> ------------------------------------------
>
>                 Key: OPENJPA-1161
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1161
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 1.0.4
>            Reporter: brian yoder
>         Attachments: screenshot-1.jpg
>
>
> After a lot of testing I have reproduced a specific scenario where the MappingRepository instances grow, and eventually an OutOfMemory error will occur.  There have been other reports of this occuring, but no response from Apache yet, so I am opening a new bug.  I will attach the code wich causes the issue, and a screen shot of the memory leaking classes.
> Note: This may be related to OPENJPA-746

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