Re[2]: [OT] conn pooling - what next?

[Rick Reumann <ma...@reumann.net>]

On Tuesday, August 27, 2002, 10:49:45 AM, Kevin wrote:

KAS> If the DBA is manually killing off your connections, then the
KAS> pool needs to be paranoid about checking to see if the connection
KAS> is available before each operation. So this adds overhead to
KAS> using the pool.

     Is there a pool that does this checking? I might to suffer the
     overhead vs having the problems we have when our DBA messes
     around and kills stuff.


KAS> In addition, consider this code:

KAS> Connection cn = pool.allocate();
KAS> Statement stmt = cn.createStatement("some sql here");
KAS> ResultSet rs = stmt.execute();

KAS> Given the above, the pool could check the state of the connection
KAS> before it returns from allocate(), but the other exception
KAS> handling would be up to you.

     I'm not really concerned with the problem of there being an error
     for the short time after the connections are killed and someone
     just got a connection and is about to use it. The problem is that
     a new connection is not able to be gotten at all after they are
     killed.

     Thanks for any more help or advice.

-- 

Rick
mailto:maillist@reumann.net


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>