svn commit: r1334532 - /commons/proper/pool/trunk/src/changes/changes.xml

[sebb]

Author: sebb
Date: Sat May  5 23:17:51 2012
New Revision: 1334532

URL: http://svn.apache.org/viewvc?rev=1334532&view=rev
Log:
Some more issues fixed in 2.0

Modified:
    commons/proper/pool/trunk/src/changes/changes.xml

Modified: commons/proper/pool/trunk/src/changes/changes.xml
URL: 
http://svn.apache.org/viewvc/commons/proper/pool/trunk/src/changes/changes.xml?rev=1334532&r1=1334531&r2=1334532&view=diff
==============================================================================
--- commons/proper/pool/trunk/src/changes/changes.xml (original)
+++ commons/proper/pool/trunk/src/changes/changes.xml Sat May  5 23:17:51 2012
@@ -52,6 +52,36 @@ clarify behaviour and improve consistenc
     <action issue="POOL-221" dev="markt" type="fix" >
       PooledObject.state does not need to be volatile.
     </action>
+    <action issue="POOL-216" dev="markt" type="update" >
+      GenericKeyedObjectPool.ensureMinIdle(K) does not need to check 
getMinIdlePerKey().
+    </action>
+    <action issue="POOL-215" dev="markt" type="fix" >
+      GenericKeyedObjectPool - multiple mutable fields not published safely.
+    </action>
+    <action issue="POOL-214" dev="markt" type="fix" >
+      GenericObjectPool.evictionPolicy not thread-safe
+    </action>
+    <action issue="POOL-212" dev="markt" type="fix" >
+      GenericObjectPool allows maxIdle &lt; minIdle
+    </action>
+    <action issue="POOL-207" dev="markt" type="fix" >
+      GenericKeyedObjectPool.clear() has unnecessary null check of 
objectDequeue
+    </action>
+    <action issue="POOL-201" dev="markt" type="fix" >
+      Classes Generic[Keyed]ObjectPoolConfig are generic - but why? 
+    </action>
+    <action issue="POOL-200" dev="markt" type="fix" >
+      GOP/GKOP don't consistently use getters to access fields
+    </action>
+    <action issue="POOL-199" dev="markt" type="fix" >
+      GOP/GKOP evict() method is not synchronised and is not thread-safe
+    </action>
+    <action issue="POOL-197" dev="markt" type="fix" >
+      PooledObject: risky init of lastBorrowTime & lastReturnTime
+    </action>
+    <action issue="POOL-196" dev="markt" type="fix" >
+      PooledObject.getActiveTimeMillis() does not synch. access to 
lastReturnTime and lastBorrowTime
+    </action>
     <action issue="POOL-194" dev="simonetripodi" type="update" 
date="2011-12-12">
       Replace synchronized blocks in PoolUtils with Read/Write locks.
     </action>