The openjpa.Multithreaded property is only for having multiple threads sharing the same EntityManager. Per the spec EMs aren't supposed to be shared across threads, but some applications do(rightly or wrongly). If you're building from the ground up, I'd suggest against it (Perhaps others on the list have an opinion). Also, there is a performance hit for setting this property to true. A properly designed application shouldn't need to set this prop.
Now on the the JDBC benchmark... shouldn't you be creating your prepared statement within the for loop? The way you have it coded currently, you're caching your prepared statement, but OpenJPA is creating a new prepared statement each time (I think?). Thanks, Rick
