[
https://issues.apache.org/jira/browse/OPENJPA-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004615#comment-13004615
]
Rick Curtis commented on OPENJPA-1161:
--------------------------------------
> (brian yoder) I tested in 1.2.0 and 1.0.4 (SNAPSHOT which is what my version
> of WebSphere uses) and JPA seems off the hook. The code doesn't leak when it
> is run standalone in JUnit. So it seems the leak occurs at the web container
> side of things. So I will open bug with IBM.
prueba -
Per Brian's last comment, this isn't a problem in OpenJPA. If you are observing
this behavior, please write a simple unit test that exhibits the problem and
attach it to a new JIRA.
Thanks,
Rick
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
