[
https://issues.apache.org/jira/browse/AMBARI-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579567#comment-13579567
]
Mahadev konar commented on AMBARI-1435:
---------------------------------------
+1 for the patch. Improves the perf by quite a bit!
> L2 Cache does not work due to Eclipse Link exception
> ----------------------------------------------------
>
> Key: AMBARI-1435
> URL: https://issues.apache.org/jira/browse/AMBARI-1435
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.2.1
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.2.2
>
> Attachments: AMBARI-1435.patch
>
>
> Turning on caching for the perf test and install.
> <properties>
> <property name="javax.persistence.jdbc.url"
> value="jdbc:postgresql://localhost/ambari" />
> <property name="javax.persistence.jdbc.driver"
> value="org.postgresql.Driver" />
> <property name="eclipselink.cache.shared.default" value="true" />
> <property name="eclipselink.cache.size.default" value="2000" />
> <!--property name="eclipselink.cache.type.default" value="" /-->
> <property name="eclipselink.query-results-cache" value="true" />
> </properties>
> I got the installation up to the installation step with every step chugging
> along at acceptable speeds.
> Except the Service State Change from INIT to INSTALLED. It was at this step
> for a very long time, however the state change did eventually happen.
> I do see exception in server logs:
> 03:29:20,145 WARN ActionScheduler that you:92 - Exception received
> javax.persistence.RollbackException: Exception [EclipseLink-7197] (Eclipse
> Persistence Services - 2.4.0.v20120608-r11652):
> org.eclipse.persistence.exceptions.ValidationException
> Exception Description: Null or zero primary key encountered in unit of work
> clone
> [org.apache.ambari.server.orm.entities.ExecutionCommandEntity@7fa85d97],
> primary key [null]. Set descriptors IdValidation or the
> "eclipselink.id-validation" property.
--
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
