This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Entity From DB / EJBs from Entity generators are broken | ||
---|---|---|---|
Product: | javaee | Reporter: | David Konecny <dkonecny> |
Component: | Persistence | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pjiricka, tzezula |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | IDE log |
Description
David Konecny
2010-04-07 02:54:13 UTC
Created attachment 96827 [details]
IDE log
I saw these exceptions before but without OutOfMemory. I will look at this. If it will be hard to do something on ap side, may be disabling ap processing during entity generation can help. I've fixed the exceptions. The OOM is PermGen, right? Probably eclipselink does lots of intern, I've downloaded sources to take a look. One question, does the wizard all modification using runModifiacationtask or does it also some changes without the lock? main code for entity from db generation is located in org.netbeans.modules.j2ee.persistence.wizard.fromdb.JavaPersistenceGenerator::runImpl() and looks like main generation is with runModificationTask usage. But can't say if something is done without a lock, need to verify. Disabling EclipseLink annotation processor (via project's UI) make the problem go away. fixed in jet-main: d200ddfcf9aa fixed in jet-main: d200ddfcf9aa Integrated into 'main-golden', will be available in build *201004090201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d200ddfcf9aa User: Tomas Zezula <tzezula@netbeans.org> Log: #183613:Entity From DB / EJBs from Entity generators are broken |