openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pinaki Poddar <ppod...@apache.org>
Subject Re: [jira] Commented: (OPENJPA-1648) Slice thread pool breaks down under high concurrency
Date Tue, 04 May 2010 21:55:21 GMT

Hi Simon,
> Since the pool is gonna go out of scope by the time flush() is done, 
I am considering to maintain a *single* (oh yes, static) thread pool. The
threads that query/flush  can all use the same pool. The default
implementation for cached thread pool is 0 core pool size, unbounded maximum
size, 60 seconds keep alive time. We can start with these values.

> I will keep on stressing the stack and see if there are more problems. 
There sure are. Thanks for your effort.



-----
Pinaki 
-- 
View this message in context: http://openjpa.208410.n2.nabble.com/jira-Created-OPENJPA-1648-Slice-thread-pool-breaks-down-under-high-concurrency-tp5005738p5005956.html
Sent from the OpenJPA Developers mailing list archive at Nabble.com.

Mime
View raw message