[ 
https://issues.apache.org/jira/browse/OPENJPA-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898973#action_12898973
 ] 

Rick Curtis commented on OPENJPA-1469:
--------------------------------------

Below is the entire list of tests that fail in the openjpa-persistence-jdbc 
bucket. To recreate the failures, enable the datacache and re-run. I'm putting 
this list here because I don't think I'll be able to get through all of them in 
the near future.

Failures that have been investigated:
org.apache.openjpa.persistence.spring.TestLibService -- OPENJPA-1767
org.apache.openjpa.jdbc.kernel.TestM2MBiVersion -- OPENJPA-1768

Failures requiring investigation:
org.apache.openjpa.persistence.graph.TestPersistentGraph
org.apache.openjpa.persistence.jdbc.query.TestNativeQueryProcedures
org.apache.openjpa.persistence.jdbc.query.TestUpdateSingleValuedAssociation
org.apache.openjpa.jdbc.kernel.TestCollectionTracking
org.apache.openjpa.persistence.embed.attrOverrides.TestAssocOverrides
org.apache.openjpa.persistence.proxy.TestDetachMerge
org.apache.openjpa.persistence.TestXMLPersistenceMetaDataParser
org.apache.openjpa.persistence.jdbc.annotations.TestEJBEmbedded
org.apache.openjpa.persistence.jdbc.annotations.TestJoinedInheritance
org.apache.openjpa.persistence.jdbc.annotations.TestManyToMany
org.apache.openjpa.persistence.jdbc.annotations.TestOneToOne
org.apache.openjpa.persistence.jpql.joins.TestEJBJoins
org.apache.openjpa.persistence.kernel.TestIndirectRecursion
org.apache.openjpa.persistence.kernel.TestPCClass
org.apache.openjpa.persistence.event.TestBeforeCommit
org.apache.openjpa.persistence.annotations.TestJoinedInheritance
org.apache.openjpa.persistence.annotations.TestManyToMany
org.apache.openjpa.persistence.annotations.TestOneToOne
org.apache.openjpa.persistence.detachment.TestDetachNoStateField
org.apache.openjpa.persistence.enhance.identity.TestMultipleLevelDerivedIdentity1
org.apache.openjpa.persistence.query.TestProjectionQueryWithIdenticalResult
org.apache.openjpa.kernel.TestEnhancedInstanceBrokerSerialization
org.apache.openjpa.kernel.TestInstanceGraphBrokerSerialization
org.apache.openjpa.persistence.detach.TestDetachCascade
org.apache.openjpa.persistence.embed.TestEmbeddable
org.apache.openjpa.persistence.jdbc.order.TestOrderColumn
org.apache.openjpa.persistence.conf.TestOverrideNonJtaDataSource
org.apache.openjpa.persistence.conf.TestSwitchConnection
org.apache.openjpa.persistence.relations.TestChainEntities
org.apache.openjpa.persistence.relations.TestEagerBidiSQL
org.apache.openjpa.persistence.relations.TestIdOrderedOneMany
org.apache.openjpa.persistence.relations.TestInverseEagerSQL
org.apache.openjpa.persistence.relations.TestLazyManyToOne
org.apache.openjpa.persistence.relations.TestManyEagerSQL
org.apache.openjpa.persistence.relations.TestManyOneAsId
org.apache.openjpa.persistence.relations.TestRelationFieldAsPrimaryKeyAndForeignKey
org.apache.openjpa.persistence.jdbc.sqlcache.TestFinderCache
org.apache.openjpa.persistence.jpql.functions.TestSetParameter
org.apache.openjpa.persistence.criteria.TestSubqueries
org.apache.openjpa.jdbc.persistence.classcriteria.TestQuerySubclass
org.apache.openjpa.persistence.jdbc.query.cache.TestNonPrimaryKeyQueryParameters

> Turn on DataCache by default
> ----------------------------
>
>                 Key: OPENJPA-1469
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1469
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: datacache
>    Affects Versions: 2.0.0-M1, 2.0.0-M2, 2.0.0-M3, 2.0.0-beta, 2.0.0-beta2, 
> 2.0.0
>            Reporter: Kevin Sutter
>            Assignee: Rick Curtis
>             Fix For: 2.1.0
>
>
> I'm proposing that we change the default behavior for the DataCache.  
> Currently, the DataCache is turned off by default.  Our competition is 
> turning on their L2 cache by default.  Thus, out-of-the-box comparisons are 
> killing us.  We have to explain the difference, get them to change the 
> configuration one way or the other for apples-to-apples comparisons, and then 
> re-run the benchmark.  By that time, it's too late.  We already lost.
> Due to the upcoming 2.0.0 release, it seems like a good time to change this 
> default.  Please comment directly to this JIRA.
> Thanks,
> Kevin

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

Reply via email to