Hi Simon, This error is due to bad choice of thread pool. java.util.concurrent package does have powerful thread pools and we should use them effectively. I have opened a new JIRA issue [1] to change the thread pool usage.
And yes, we do not need to create a pool for every flush. I will fix both the outage and repeated creation of thread pool. [1] https://issues.apache.org/jira/browse/OPENJPA-1648 ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/Spring-3-0-2-OpenJPA-2-0-Slice-OutOfMemoryError-shortly-after-pounding-1000-threads-to-the-system-tp5000822p5005774.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
