> 1 million order inserts (Order - Customer tables, many to one, Order
sharded to 3 slices, customer
> replicated. Data cache 1000 customers). No sweat. No leak.
Good.
Really appreciate your interest in Slice and your contribution to improve
its quality/robustness.
Here are few tips that will exercise the 'weak' points
a) update instances that are @Replicated e.g. Customer, occasionally.
b) use queries that uses other persistent entity as parameter. For example,
EntityManager em = ...;
Customer customer = em.find(Customer.class, 12345);
String jpql = "select o from PurchaseOrder o where o.customer=:c order
by o.placedDate";
List<PurchaseOrder> orders = em.createQuery(jpql, PurchaseOrder.class)
.setParameter("c",
customer)
.getResultList();
And, of course, it will be great to see the same test application running on
a single database.
-----
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-tp5000822p5015708.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
