openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <>
Subject [jira] Commented: (OPENJPA-536) getMetaData() causes OutOfMemoryError under some cases
Date Tue, 01 Apr 2008 01:58:24 GMT


Albert Lee commented on OPENJPA-536:


First of all, thank you of your contribution to the solution of this problem.

I assume the last patch (i.e. 364202.patch) contains ALL the artifacts including the solutions
and the test case for verification.

>From looking at 364202.patch, it is very difficult to figure out what are the changes
in due to formating differences between the before and after files.
If you can submit a patch that shows only the necessary changes, it would greatly speed up
the code review process for the committer to help you to commit the change.

Albert Lee.

> getMetaData() causes OutOfMemoryError under some cases
> ------------------------------------------------------
>                 Key: OPENJPA-536
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.0.2, 1.0.3
>         Environment: Sun JDK 5
>            Reporter: Amy Yang
>            Priority: Blocker
>         Attachments: 364202.patch, InheritanceComparator.diff,, MetaDataRepository.diff
> There are 3 classes: Item, Artist and Person. Artist extends Person. 
> Invoking JPAFacadeHelper.getMetaData(emf, Item.class) will cause OutOfMemoryError thrown
by org.apache.openjpa.meta.MetaDataRepository.processBuffer().

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

View raw message