On Aug 29, 2006, at 4:13 PM, Dain Sundstrom wrote:
It doesn't look like AbstractSinglePoolConnectionInterceptor ever uses the writeLock in the ReentrantReadWriteLock so it may be possible to replace that lock with a simpler ReentrantLock.
It is calling writeLock() in setPartitionMaxSize() --jason
