This may be a tough one and thank you for sending the blocking thread stack. The QueryContext is shared by the parallel queries. The stack points out that query context is deadlocked as Executors calling QueryContext (which has its own lock) method on different threads. Slice has not imposed any major change on kernel's behavior (on threading or otherwise). But this current limitation might. The easy (and escapist) way out is to fall back on sequential query execution when openjpa.Multithreaded is set.
Thoughts? -- View this message in context: http://n2.nabble.com/slices-hangs-if-run-with-Multithreaded%3Dtrue-tp1645757p1648719.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
