Can you try to put your properties directly in the persistence.xml file to see if that helps? If not, enable trace and run through a few queries... That should help figure out what is going on.
Sent from my iPhone On Aug 30, 2013, at 1:38 PM, tlianza <nab...@lianza.org> wrote: > Rick Curtis wrote >> Unless you omitted the relevant portions of your persistence.xml file, it >> looks like you didn't enable the openjpa.QueryCache? Do you not have any >> persistent properties set? > > Ah - yes sorry we programmatically set those and they're stored in a > different config file. The properties we set are as follows: > > <entry key="openjpa.Log" value="slf4j"/> > <entry key="openjpa.ConnectionFactoryProperties" > value="printParameters=true"/> > <entry key="openjpa.DataCache" value="true(EnableStatistics=true)"/> > <entry key="openjpa.QueryCache" value="true(EnableStatistics=true)"/> > <entry key="openjpa.RemoteCommitProvider" value="sjvm"/> > <entry key="openjpa.RestoreState" value="true"/> > <entry key="openjpa.RetainState" value="true"/> > <entry key="openjpa.jdbc.SchemaFactory" value="native(ForeignKeys=true)"/> > <entry key="openjpa.BrokerImpl" value="EvictFromDataCache=true"/> > <entry key="openjpa.jdbc.DBDictionary" value="postgres"/> > <entry key="openjpa.Instrumentation" > value="jmx(Instrument='DataCache,QueryCache,QuerySQLCache')"/> > > Thanks again! > > Tom > > > > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Using-QueryCache-still-seeing-queries-sent-to-the-DB-tp7584807p7584824.html > Sent from the OpenJPA Users mailing list archive at Nabble.com.