[
https://issues.apache.org/jira/browse/OOZIE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678608#comment-13678608
]
Robert Kanter commented on OOZIE-1377:
--------------------------------------
Looks like you missed a version number at the end; it should be
$\{openjpa.version\} instead.
{code:xml}
+ <plugin>
+ <groupId>org.apache.openjpa</groupId>
+ <artifactId>openjpa-maven-plugin</artifactId>
+ <version>2.2.2</version>
+ </plugin>
{code}
+1 pending that change and Jenkins
> OpenJPA runtime enhancement should be disabled and update OpenJPA to 2.2.2
> --------------------------------------------------------------------------
>
> Key: OOZIE-1377
> URL: https://issues.apache.org/jira/browse/OOZIE-1377
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.2
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: OOZIE-1377.patch, OOZIE-1377.patch, OOZIE-1377.patch
>
>
> The persistence.xml has runtime enhancement enabled.
> We are running into OOM (due to a leak in OpenJPA) under certain usage
> patterns.
> While we are enhancing the classes at build time, the problem still persists.
> After checking with the openjpa folks
> (http://mail-archives.apache.org/mod_mbox/openjpa-users/201305.mbox/%3CCABH8ernmKrQMf_2JMdOdnd6Xh7%3DDRFwSf6s4NL8tuE0ZHfZunA%40mail.gmail.com%3E)
> we disabled the runtime enhancement and the OOM issue went away.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
