On 8/17/18 10:13 AM, Gary Gregory wrote:
A CopyOnWriteArrayList won't work since it does not support remove()...
but the idea is to replace the ArrayList with a java.utl.concurrent
structure...
Interesting idea. The thing to check is how method activations
depend on the locks. A quick look indicates that there is a mix of
"lock for snapshot" and "lock for integrity." j.u.concurrent things
tend to work nicely for the second but not for the first.
Phil
Gary
On Fri, Aug 17, 2018 at 11:05 AM Gary Gregory <garydgreg...@gmail.com>
wrote:
Hi All and Phil:
In [DBCP] Abandoned trace we use an Array with synchronized blocks. Should
we replace this usage with a CopyOnWriteArrayList and no custom blocks?
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
