Turns out adding jvm option -XX:+AlwaysLockClassLoader appears to resolve issue.
>From http://docs.oracle.com/javase/7/docs/technotes/guides/lang/cl-mt.html It says: Troubleshooting If your product ships and appears to have problems due to incomplete handling of critical sections, you can use a new VM flag -XX:+AlwaysLockClassLoader. This flag reverts to locking the class loader lock before invoking your custom class loader's findClass() or loadClass() method, even for class loaders that register as parallel capable. The correct fix however would be to follow the guidelines in that post. -- View this message in context: http://openjpa.208410.n2.nabble.com/JDK-1-7-seems-to-be-causing-an-issue-with-latest-snapshot-tp7581417p7584744.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
