Marc, based on the causes mentioned on the link you provided, I'd guess
you're using the same EntityManager instance from multiple threads. Per
JPA spec, EntityManager instances are not thread-safe.
The way in which EntityManagers use JDBC connections is configurable and
explained here:
http://openjpa.apache.org/docs/latest/manual/ref_guide_dbsetup_retain.html
That configuration however is not likely to help with the error you're
seeing, if your application shares EntityManagers across multiple threads.
Marc Siegel wrote:
Hi Patrick, et al,
This problem is probably explained by the info here:
http://www.sqlite.org/cvstrac/wiki?p=LibraryRoutineCalledOutOfSequence
According to results from other project mailing lists found via Google
search, use of sqlite data structures from a thread pool can trigger
situations that cause this error.
Is OpenJpa by default using its JDBC connections from a thread pool?
Is this configurable via DBDictionary properties or methods?
Thanks,
-Marc
