User: mulder
Date: 00/11/15 10:03:09
Modified: src/main/org/jboss/minerva/pools ObjectPool.java
Log:
Don't release an object automatically on an error - the client must
still catch the error and close the object.
Revision Changes Path
1.16 +3 -5 jboss/src/main/org/jboss/minerva/pools/ObjectPool.java
Index: ObjectPool.java
===================================================================
RCS file:
/products/cvs/ejboss/jboss/src/main/org/jboss/minerva/pools/ObjectPool.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- ObjectPool.java 2000/10/25 17:04:11 1.15
+++ ObjectPool.java 2000/11/15 18:03:09 1.16
@@ -28,7 +28,7 @@
* <LI>Shut it down</LI>
* </OL>
* @see org.jboss.minerva.pools.PooledObject
- * @version $Revision: 1.15 $
+ * @version $Revision: 1.16 $
* @author Aaron Mulder ([EMAIL PROTECTED])
*/
public class ObjectPool implements PoolEventListener {
@@ -696,14 +696,12 @@
}
/**
- * If the object had an error, we assume this will propogate and preclude it
- * from being closed, so we will close it. If the invalidateOnError flag
- * is set, the object will be removed from the pool entirely.
+ * If the invalidateOnError flag is set, the object will be removed from
+ * the pool entirely when the client has finished with it.
*/
public void objectError(PoolEvent evt) {
if(invalidateOnError || evt.isCatastrophic())
markObjectAsInvalid(evt.getSource());
- releaseObject(evt.getSource());
}
/**
