In Jrun 3.1 you could set a parameter 'maxUse' on the JDBC connection pool the defined how many times a connection would be assigned before being automatically closed by the pool and the database resources cleaned up.
In 4.0, we can't find anything equivalent and are having problems with the JRun connections pools.
Specifically, JRun seems to have strange way of determining which connections get removed from the pool. We've observed that JRun will never close the first 'n' connections, where 'n' is the connection pool min size. These connections are always held open, even if there is no activity.
This is causing problems because this means we have open database processes for weeks or months and the DBAs tell us this is placing an unnecessary burden on the database. In particular, the amount of RAM each oracle connection is holding. They want us to cycle them daily, 8 hours max if possible.
Any thoughts on how to get JRun to release these older connections?
Note: the reaping of the pool is working, just not the first connections in the pool. Setting the min size to 0 doesn't help, the first connection is never closed.
Thanks,
Chris
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
