>> a) I get 5 connections and then I Thread.sleep for 30 seconds before >> closing the obtained connections. On the same time I monitor the number >> of open sessions on my DB which is ALWAYS 5. Shouldn't this number be >> reduced to '2' after the 5000millis (when eviction mechanism initiates)?
>No, you've got that backwards. The only connections available for eviction >in this way are those that are sitting idle in the pool. If you have >borrowed (via getConnection), but not returned (via Connection.close()) the >connection, it can't be evicted. It appears that the settings in 'GenericObjectPool' for eviction are related to idle connections in the pool (not borrowed). Is there a way to drop/remove connections that have been 'borrowed' after they have sat idle for a certain amount of time? I want to prevent a process from holding a connection indefinately. thanks Paul
