Hi All,
I have question about JDBC pooling in WebSphere 7. I have a JDBC pool set up connecting to oracle database 11.2, I have min/max set at 1/150 and ReapTime 180 and Unused TimeOut at 1800 Seconds and AgedTimeOut to 0(zero), PurgePolicy - Entire Pool.
If I understand correctly these setting should run a pool maintneance thread every 3 minutes and clean up any connections that are inactive for 30 minutes. What we have been seeing is that there are too many inactive connections (around 200) on the Database side that are not being cleaned up, should the application/websphere clean those up on database side, intermittently we are seeing them cleaned up on database side but cannot tell what is perfoming that.
Also is there a log with in WebSphere that can show that the unused timeout cleaned up idle connections. One last, is there a way to terminate a database connection if its hung or takes long (say 5 minutes)