Hi again.
Found the solution to my problem.
Adding a QueryCache seems to have helped us listing entities in different
threads.
The Eviction with timestamp is crusial for performance and seems to work
well for us.
property name=openjpa.QueryCache value=true(CacheSize=1000,
SoftReferenceSize=0,
Hi Rick.
At the moment we have a problem with EntityManagers not being in sync. We
have an application where you could update user data. And when we reload
the page with the user data listed. These are elements connected to the
user data and are them self another entity entirely and we fetch them
Hi again.
Just wanted to add that we have reduced the settings to this
property name=openjpa.DataCache value=true(CacheSize=1000,
SoftReferenceSize=0)/
property name=openjpa.QueryCache value=false/
property name=openjpa.Log value=DefaultLevel=INFO, Runtime=INFO,
Tool=INFO, SQL=INFO/
property
Daniel -
Yes, I'd be interested in seeing the full exception. That being said,
you're probably safe just turning off the DynamicDataStructs . In our
performance testing, we never observed an improvement when that property is
enabled.
Since we're on the topic of properties, I'd also recommend
Hi.
I'd used OpenJPA for my projects for a while now and started to use it at
work.
Our service runs on Tomcat and have a lot of users. So after implementing
OpenJPA for a few months we are now in the testing phase.
During the stress test adding a few hundred records using different tomcat
